restorecon /dev/nvidia-uvm

Should fix the problem.  This is a race condition between boinc and udev as far as fixing the label on this nvidia device.

Indeed,
here is the output of restorecon -v /dev/nvidia-uvm.
restorecon reset /dev/nvidia-uvm context system_u:object_r:device_t:s0->system_u:object_r:xserver_misc_device_t:s0

That's strange since I have done a touch /.autorelabel a few days ago.

Restart of the service seems to work without error messages after removing first post custom rules with semodule -r boinc-gul

Thanks

Hi Daniel,
Here is some additional information. 

Despite the local policy I have added, boinc was still unable to see the gpu when rebooting. BUT it works fine after restarting boinc-client.service.

So I have reinstalled selinux-policy and selinux-policy-targeted 3.12.1-183.fc20 and put selinux to permissive mode. 

After a reboot, /dev/nvidia-uvm has again the wrong context.
Here are audit2allow found rules for boinc:
allow boinc_t device_t:chr_file { write getattr setattr read create open ioctl }
;
allow boinc_t device_t:dir { write add_name };
allow boinc_t modules_conf_t:dir read;
allow boinc_t modules_conf_t:file { read open };
allow boinc_t modules_object_t:file { read open };
allow boinc_t self:capability { mknod chown };
allow boinc_t sysctl_modprobe_t:file { read getattr open };

Nevertheless, it is NOT working with selinux set to enforced mode.

Cheers,
GuL

*** Bug 1140253 has been marked as a duplicate of this bug. ***

Created attachment 943764 [details]
grep 1412356 /var/log/audit/audit.log | grep boinc | grep AVC > boinc-AVC.log

Hi, after updating to selinux-policy-3.12.1-188.fc20, full selinux relabel and reboot, I still have the following errors concerning boinc.

#============= boinc_t ==============
allow boinc_t device_t:chr_file { write getattr setattr read create open ioctl }
;
allow boinc_t device_t:dir { write add_name };
allow boinc_t modules_conf_t:dir read;
allow boinc_t modules_conf_t:file { read open };
allow boinc_t modules_object_t:file { read open };
allow boinc_t self:capability { mknod chown };
allow boinc_t sysctl_modprobe_t:file { read getattr open };

audit.log has been restricted to the relevant date.

Cheers

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.