Bug 801282 - SELinux is preventing /sbin/dhclient from read, write access on the None /dev/dri/card0.
SELinux is preventing /sbin/dhclient from read, write access on the None /dev...
Status: CLOSED CANTFIX
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
16
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Miroslav Grepl
Fedora Extras Quality Assurance
abrt_hash:c6d17ee6a6716ef37807229283f...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-08 02:36 EST by hkoba
Modified: 2012-03-08 10:58 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-03-08 10:00:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: description (2.22 KB, text/plain)
2012-03-08 02:36 EST, hkoba
no flags Details

  None (edit)
Description hkoba 2012-03-08 02:36:15 EST
libreport version: 2.0.8
executable:     /usr/bin/python
hashmarkername: setroubleshoot
kernel:         3.2.9-1.fc16.x86_64
reason:         SELinux is preventing /sbin/dhclient from read, write access on the None /dev/dri/card0.
time:           2012年03月09日 00時35分31秒

description:    Binary file, 2275 bytes
Comment 1 hkoba 2012-03-08 02:36:18 EST
Created attachment 568527 [details]
File: description
Comment 2 Daniel Walsh 2012-03-08 10:00:28 EST
This is a leaked file descriptor from whatever app launched dhclient.  Please update your machine to the latest code.

yum -y update
Comment 3 hkoba 2012-03-08 10:38:04 EST
Hmm, I use yum-cron and my system is up-to-date.

Anyway, I understand it is fd leakage problem. I agree to close this.
Thank you for your comment.
Comment 4 Daniel Walsh 2012-03-08 10:46:48 EST
Well it would be nice to know who is leaking it.

I actually blogged on this last night..


http://danwalsh.livejournal.com/53603.html
Comment 5 hkoba 2012-03-08 10:58:33 EST
Thank you for your good article.

I now understand how *_CLOEXEC flag is important. Thank you:-)

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