Bug 456137 - selinux barfes on new yum update (21 Jul 08) on gam_server
selinux barfes on new yum update (21 Jul 08) on gam_server
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
x86_64 Linux
low Severity urgent
: ---
: ---
Assigned To: Daniel Walsh
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-21 13:25 EDT by Joel
Modified: 2008-11-17 15:35 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-17 15:35:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
output of sealert -l b115b681-c98f-449d-9e5f-f2fc7123666a (2.50 KB, text/plain)
2008-07-21 14:04 EDT, Joel
no flags Details

  None (edit)
Description Joel 2008-07-21 13:25:27 EDT
Description of problem:
with today's (21 Jul 2008) yum update, selinux has a cow regarding gam_server
and inotify. 

SELinux is preventing gam_server (unlabeled_t) "read" to inotify (inotifyfs_t).

SELinux suggests typing restorecon -v 'inotify' to fix.  There is no inotify? 
What is it talking about?  How about real messages that tell the exact path of
the resource?

Version-Release number of selected component (if applicable):

Policy RPM                    selinux-policy-3.3.1-78.fc9

How reproducible:

It reproduces itself about 5 times per second.

Steps to Reproduce:
1.  Watch stupid alert messages make your desktop unusable as they come several
times per second.
Actual results:

See above

Expected results:

System gets tested?  This is the second bad yum update in four days (last was
bad xulrunner update).

Additional info:
Comment 1 Joel 2008-07-21 14:04:38 EDT
Created attachment 312285 [details]
output of sealert -l b115b681-c98f-449d-9e5f-f2fc7123666a
Comment 2 Daniel Walsh 2008-07-24 07:56:48 EDT
Fixed in selinux-policy-3.3.1-79.fc9
Comment 3 Joel 2008-11-15 20:31:39 EST
Can this be closed now?  I don't think it is a problem anymore for several months
Comment 4 Daniel Walsh 2008-11-17 15:35:45 EST
If you confirm a fix, you can close the bug.

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