Bug 760355 - SELinux is preventing /usr/bin/boinc_client from 'open' accesses on the chr_file nvidiactl.
Summary: SELinux is preventing /usr/bin/boinc_client from 'open' accesses on the chr_f...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:351c827e1ac...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-05 21:47 UTC by Doug Hutcheson
Modified: 2011-12-06 09:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 09:09:26 UTC
Type: ---


Attachments (Terms of Use)

Description Doug Hutcheson 2011-12-05 21:47:01 UTC
SELinux is preventing /usr/bin/boinc_client from 'open' accesses on the chr_file nvidiactl.

*****  Plugin device (91.4 confidence) suggests  *****************************

If you want to allow boinc_client to have open access on the nvidiactl chr_file
Then you need to change the label on nvidiactl to a type of a similar device.
Do
# semanage fcontext -a -t SIMILAR_TYPE 'nvidiactl'
# restorecon -v 'nvidiactl'

*****  Plugin catchall (9.59 confidence) suggests  ***************************

If you believe that boinc_client should be allowed open access on the nvidiactl chr_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep boinc_client /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:boinc_t:s0
Target Context                system_u:object_r:device_t:s0
Target Objects                nvidiactl [ chr_file ]
Source                        boinc_client
Source Path                   /usr/bin/boinc_client
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           boinc-client-6.10.58-3.r22930svn.fc15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.16-48.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.41.1-1.fc15.x86_64 #1
                              SMP Fri Nov 11 21:36:28 UTC 2011 x86_64 x86_64
Alert Count                   1
First Seen                    Tue 06 Dec 2011 07:36:48 EST
Last Seen                     Tue 06 Dec 2011 07:36:48 EST
Local ID                      ccebca59-0214-41b9-b402-ece662538db9

Raw Audit Messages
type=AVC msg=audit(1323121008.664:236): avc:  denied  { open } for  pid=7485 comm="boinc_client" name="nvidiactl" dev=devtmpfs ino=19908 scontext=system_u:system_r:boinc_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=chr_file


type=SYSCALL msg=audit(1323121008.664:236): arch=x86_64 syscall=open success=no exit=EACCES a0=7fff6c3b5c10 a1=2 a2=7fff6c3b5c1e a3=0 items=0 ppid=1 pid=7485 auid=4294967295 uid=492 gid=489 euid=492 suid=492 fsuid=492 egid=489 sgid=489 fsgid=489 tty=(none) ses=4294967295 comm=boinc_client exe=/usr/bin/boinc_client subj=system_u:system_r:boinc_t:s0 key=(null)

Hash: boinc_client,boinc_t,device_t,chr_file,open

audit2allow

#============= boinc_t ==============
#!!!! This avc is allowed in the current policy

allow boinc_t device_t:chr_file open;

audit2allow -R

#============= boinc_t ==============
#!!!! This avc is allowed in the current policy

allow boinc_t device_t:chr_file open;

Comment 1 Doug Hutcheson 2011-12-05 21:52:04 UTC
I am using boinc for the first time, having installed it yesterday. I applied the suggested fix the first time this error occurred, but it does not seem to remain in force between reboots.

The suggested fix was applied as:
#grep boinc_client /var/log/audit/audit.log | audit2allow -M mypol
#semodule -i mypol.pp

Comment 2 Miroslav Grepl 2011-12-06 09:09:26 UTC
The is a problem with nvidia on F15. We fixed this on F16 where this nvidia devices get a proper label.

# restorecon -R -v /dev/nvidia*

will fix labeling.

Comment 3 Doug Hutcheson 2011-12-06 09:37:04 UTC
Thanks for the quick and helpful response.


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