Bug 521728 - setroubleshoot: SELinux is preventing ldconfig "write" access to to a leaked file descriptor on /home/username/.config/exaile/exaile.log
Summary: setroubleshoot: SELinux is preventing ldconfig "write" access to to a le...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: exaile
Version: rawhide
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:2ae73f6177d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-08 00:34 UTC by Filippo Racca
Modified: 2009-10-21 02:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-21 02:24:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Filippo Racca 2009-09-08 00:34:39 UTC
The following was filed automatically by setroubleshoot:

Sommario:

SELinux is preventing ldconfig "write" access to to a leaked file descriptor on
/home/Pippo/.config/exaile/exaile.log

Descrizione dettagliata:

[ldconfig has a permissive type (ldconfig_t). This access was not denied.]

SELinux denied access requested by the ldconfig command. It looks like this is
either a leaked descriptor or ldconfig output was redirected to a file it is not
allowed to access. Leaks usually can be ignored since SELinux is just closing
the leak and reporting the error. The application does not use the descriptor,
so it will run properly. If this is a redirection, you will not get output in
the /home/Pippo/.config/exaile/exaile.log. You should generate a bugzilla on
selinux-policy, and it will get routed to the appropriate package. You can
safely ignore this avc.

Abilitazione accesso in corso:

You can generate a local policy module to allow this access - see FAQ
(http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385)

Informazioni aggiuntive:

Contesto della sorgente       unconfined_u:unconfined_r:ldconfig_t:s0-s0:c0.c102
                              3
Contesto target               unconfined_u:object_r:gnome_home_t:s0
Oggetti target                /home/Pippo/.config/exaile/exaile.log [ file ]
Sorgente                      ldconfig
Percorso della sorgente       /sbin/ldconfig
Porta                         <Sconosciuto>
Host                          (removed)
Sorgente Pacchetti RPM        glibc-2.10.90-20
Pacchetti RPM target          
RPM della policy              selinux-policy-3.6.30-4.fc12
Selinux abilitato             True
Tipo di policy                targeted
MLS abilitato                 True
Modalità Enforcing           Enforcing
Nome plugin                   leaks
Host Name                     (removed)
Piattaforma                   Linux (removed) 2.6.31-0.204.rc9.fc12.i686 #1 SMP Sat
                              Sep 5 21:01:10 EDT 2009 i686 i686
Conteggio avvisi              1
Primo visto                   mar 08 set 2009 02:27:00 CEST
Ultimo visto                  mar 08 set 2009 02:27:00 CEST
ID locale                     a5352c4b-59a5-402a-bd32-e27c0a31bf9a
Numeri di linea               

Messaggi Raw Audit            

node=(removed) type=AVC msg=audit(1252369620.457:118): avc:  denied  { write } for  pid=7280 comm="ldconfig" path="/home/Pippo/.config/exaile/exaile.log" dev=dm-0 ino=160776 scontext=unconfined_u:unconfined_r:ldconfig_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:gnome_home_t:s0 tclass=file

node=(removed) type=SYSCALL msg=audit(1252369620.457:118): arch=40000003 syscall=11 success=yes exit=0 a0=81f2928 a1=81f29a8 a2=81f19c0 a3=81f29a8 items=0 ppid=7279 pid=7280 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=1 comm="ldconfig" exe="/sbin/ldconfig" subj=unconfined_u:unconfined_r:ldconfig_t:s0-s0:c0.c1023 key=(null)


audit2allow suggests:

#============= ldconfig_t ==============
allow ldconfig_t gnome_home_t:file write;

Comment 1 Filippo Racca 2009-09-08 00:37:18 UTC
Received this message while opening for the first time Exaile on a F12 rawhide.

Comment 2 Daniel Walsh 2009-09-08 23:16:18 UTC
Not sure what is going on here,   But the tool that launched ldconfig is leaking an open file descriptor.

Is this firefox?

Comment 3 Daniel Walsh 2009-10-20 20:53:56 UTC
exaile should close all of its open file descriptors on exec


fcntl(fd, F_SETFD, FD_CLOEXEC)

Comment 4 Deji Akingunola 2009-10-20 23:09:42 UTC
exaile seems to be properly using the python logging facility for handling its log files. It could be the app (exaile) crashes before it gets to closing its opened log.

@Filipo,
Has you had exaile crashing on you before you were able to properly exit it?

Comment 5 Filippo Racca 2009-10-21 01:15:13 UTC
Sorry, I don't remember exactly: it happened the moment I started Exaile via the Application menu. But now with the latest updates everything seems to work. Unfortunately I'm unable to confirm what was the update that resolved the problem...If it can be of any help Exaile is now version 0.3.0-1.

Comment 6 Deji Akingunola 2009-10-21 02:24:44 UTC
Thanks for info, I guess we can close the bug then.


Note You need to log in before you can comment on or make changes to this bug.