Description of problem: selinux-autorelabel (fixfiles to be exact) tried to create a file (/proc/self/fd/1) on the proc fs: 22:52:41 localhost audit[282]: AVC avc: denied { write } for pid=282 comm="fixfiles" name="fd" dev="proc" ino=13899 scontext=sys.id:sys.role:seutils.setfiles.subj:s0 tcontext=sys.id:sys.role:seutils.setfiles.subj:s0 tclass=dir permissive=1 Apr 29 22:52:41 localhost audit[282]: AVC avc: denied { add_name } for pid=282 comm="fixfiles" name="1" scontext=sys.id:sys.role:seutils.setfiles.subj:s0 tcontext=sys.id:sys.role:seutils.setfiles.subj:s0 tclass=dir permissive=1 Apr 29 22:52:41 localhost audit[282]: AVC avc: denied { create } for pid=282 comm="fixfiles" name="1" scontext=sys.id:sys.role:seutils.setfiles.subj:s0 tcontext=sys.id:sys.role:seutils.setfiles.subj:s0 tclass=file permissive=1 Apr 29 22:52:41 localhost audit[282]: AVC avc: denied { associate } for pid=282 comm="fixfiles" name="1" scontext=sys.id:sys.role:seutils.setfiles.subj:s0 tcontext=sys.id:sys.role:fs.proc.fs:s0 tclass=filesystem permissive=1 Version-Release number of selected component (if applicable): policycoreutils-2.6-5.fc26.x86_64 How reproducible: fixfiles onboot && reboot journalctl -b -1 | grep -i denied Steps to Reproduce: 1. 2. 3. Actual results: fixfiles is trying to create /proc/self/fd/1 file Expected results: fixfiles shouldnt have to attempt to create /proc/self/fd/1 Additional info: Might be something that can and should be configured in selinux-autorelabel.service unit?
Created attachment 1276370 [details] proposed changes to fixfiles As mentioned earlier, I've been working on a revision to fixfiles. I don't understand why you have this problem, but the change that I think caused it was wrong anyway. Would you like to test this version?
Yes, that version no longer attempts to create the file. So it looks to have fixed the issue.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.