+++ This bug was initially created as a clone of Bug 637613 +++


Summary:

SELinux is preventing /usr/bin/runcon "transition" access on /bin/mount.

Detailed Description:

SELinux denied access requested by runcon. It is not expected that this access
is required by runcon and this access may signal an intrusion attempt. It is
also possible that the specific version or configuration of the application is
causing it to require additional access.

Allowing Access:

You can generate a local policy module to allow this access - see FAQ
(http://docs.fedoraproject.org/selinux-faq-fc5/#id2961385) Please file a bug
report.

Additional Information:

Source Context                system_u:system_r:init_t:s0
Target Context                system_u:system_r:unconfined_t:s0
Target Objects                /bin/mount [ process ]
Source                        runcon
Source Path                   /usr/bin/runcon
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           coreutils-8.4-8.fc13
Target RPM Packages           util-linux-ng-2.17.2-8.fc13
Policy RPM                    selinux-policy-3.7.19-57.fc13
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Plugin Name                   catchall
Host Name                     (removed)
Platform                      Linux (removed) 2.6.34.7-56.fc13.i686 #1 SMP
                              Wed Sep 15 03:33:58 UTC 2010 i686 i686
Alert Count                   2
First Seen                    Sun 26 Sep 2010 06:10:36 PM BRT
Last Seen                     Sun 26 Sep 2010 06:14:09 PM BRT
Local ID                      7d709a2e-884c-49fb-80b4-693a9643e62a
Line Numbers                  

Raw Audit Messages            

node=(removed) type=AVC msg=audit(1285535649.544:10): avc:  denied  { transition } for  pid=1099 comm="runcon" path="/bin/mount" dev=sda3 ino=15421 scontext=system_u:system_r:init_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=process

node=(removed) type=SYSCALL msg=audit(1285535649.544:10): arch=40000003 syscall=11 success=no exit=-13 a0=bfa2b989 a1=bfa2bb34 a2=bfa2bb4c a3=bfa2bf57 items=0 ppid=1085 pid=1099 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runcon" exe="/usr/bin/runcon" subj=system_u:system_r:init_t:s0 key=(null)



Hash String generated from  catchall,runcon,init_t,unconfined_t,process,transition
audit2allow suggests:

#============= init_t ==============
allow init_t unconfined_t:process transition;

--- Additional comment from dwalsh onMon Sep 27 13:04:06 EDT 2010 ---
Why are you using runcon to run mount as unconfined_t.  This is not supported.

--- Additional comment from dwalsh onMon Sep 27 13:05:01 EDT 2010 ---
*** Bug 637610 has been marked as a duplicate of this bug. ***

--- Additional comment from dwalsh onMon Sep 27 13:06:10 EDT 2010 ---
It also looks like you might have a labeling problem.  Your init script should not be running as init_t but as initrc_t.

You might want to run 

restorecon -R -v /etc

Or relabel the entire system

fixfiles restore

--- Additional comment from leon.kacowicz onMon Sep 27 13:18:34 EDT 2010 ---

I have no idea. The fact is: I made a fresh install of Fedora 13 and then I tried to install the ATI Graphics Driver, I think it made SELinux signal that problem.
My card is ATI Radeon HD 4350. Hope that helps.

Thanks

(In reply to comment #1)
> Why are you using runcon to run mount as unconfined_t.  This is not supported.

--- Additional comment from dwalsh onMon Sep 27 13:25:48 EDT 2010 ---
Leon fix the labelling and I think you will be ok.

--- Additional comment from leon.kacowicz onMon Sep 27 13:30:05 EDT 2010 ---
What is "labelling" and how do I fix it?
Thanks
(In reply to comment #5)
> Leon fix the labelling and I think you will be ok.

--- Additional comment from dwalsh onMon Sep 27 14:07:25 EDT 2010 ---
SELinux is a system that puts labels on every file on your disk.  Sometimes the labeling can get screwed up.  The safest way to relabel the file system is to login as root and execute

# touch /.autorelabel; reboot

This could take a decent amount of time, depending on how large your system is.
You should not need to do this again.  I have no idea how your system got mislabeled.