Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1551842
Summary: | SELinux is preventing plymouthd from 'map' accesses on the chr_file /dev/fb0. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Sullivan <jsrhbz> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 27 | CC: | benjamin.masse, c.crispino8611, chad.schroeder, dwalsh, extras-qa, juanreyes, lvrabec, marc.jadoul, marlls1989, mgrepl, mijail, mikhail.v.gavrilov, pixxxx, plautrba, pmoore, soopace, tlindsay42 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:e462dbee4e3ba9367a2778f507b3493afbdd7753b3ee87b8ff109d34c4ff34dd;VARIANT_ID=workstation; | ||
Fixed In Version: | selinux-policy-3.13.1-283.28.fc27 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1517405 | Environment: | |
Last Closed: | 2018-03-20 18:15:18 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Sullivan
2018-03-06 01:28:23 UTC
bug 1517405 was CLOSED ERRATA, claiming a fix in selinux-policy-3.13.1-283.18.fc27 or perhaps selinux-policy-3.13.1-283.19.fc27. As reported in comments on that bug, people were still seeing this in 283.21 and 283.24. I myself see exactly the same error in the journal on shutdown (and plymouth doesn't appear to work at boot or at shutdown, though I'm sure is was working earlier in the year): Mar 05 02:51:04 kanargh.hell audit[14824]: AVC avc: denied { map } for pid=14824 comm="plymouthd" path="/dev/fb0" dev="devtmpfs" ino=14372 scontext=system_u:system_r:plymouthd_t:s0 tcontext=system_u:object_r:framebuf_device_t:s0 tclass=chr_file permissive=0 That's with 283.24, and I can't see any mention of a later fix in the 283.26 changelog on koji. selinux-policy-3.13.1-283.27.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-32ebae3424 Tried 283.27. Don't think I'm getting the map denial any more. plymouth still isn't working, but that's almost certainly a bug in either plymouthd or a configuration problem. (There is a very brief flicker of life from it during boot, which sounds like bug 1396767.) *However*, when I add "plymouth:debug" to the kernel commandline, I now see: Mar 08 03:18:10 kanargh.hell audit[548]: AVC avc: denied { write } for pid=548 comm="plymouthd" name="plymouth-debug.log" dev="sda7" ino=2490727 scontext=system_u:system_r:plymouthd_t:s0 tcontext=system_u:object_r:var_log_t:s0 tclass=file permissive=0 ...which is probably less than helpful. (There's enough information that makes it to the journal for me to be getting on with, but asking it to do direct logging ought to work too.) selinux-policy-3.13.1-283.27.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-32ebae3424 And can we get a change to allow plymouth-debug.log too? This appears to do the trick: --- serefpolicy-3.13.1/policy/modules/contrib/plymouthd.fc-orig 2018-03-08 23:44:40.044908194 +0000 +++ serefpolicy-3.13.1/policy/modules/contrib/plymouthd.fc 2018-03-08 23:45:29.347150334 +0000 @@ -8,6 +8,7 @@ /var/run/plymouth(/.*)? gen_context(system_u:object_r:plymouthd_var_run_t,s0) /var/log/boot\.log.* gen_context(system_u:object_r:plymouthd_var_log_t,mls_systemhigh) +/var/log/plymouth-debug\.log.* gen_context(system_u:object_r:plymouthd_var_log_t,mls_systemhigh) /usr/sbin/plymouthd -- gen_context(system_u:object_r:plymouthd_exec_t,s0) selinux-policy-3.13.1-283.28.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-32ebae3424 Ping. 283.28 doesn't appear to have changed. Can we please allow plymouth-debug.log for the next release? selinux-policy-3.13.1-283.28.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-32ebae3424 selinux-policy-3.13.1-283.28.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. |