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 1648978
Summary: | SELinux is preventing plymouthd from 'getattr' accesses on the diretório /sys/firmware/efi/efivars. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | flaviohenriquedesousaribeiro |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | alex.bramford, alon1.dotan, artemio.silva, AsshatAdmiral, bill_pachc, danielsvpeter, dominik, dwalsh, ep, goodmirek, hobbes1069, jwilliams, jylo06g, lvrabec, mailinglists35, mati865, matthias.andree, mgrepl, mike, mike, milan.kerslager, paul.destefano-redhat2, plautrba, ppywlkiqletw, redhat, samdraiz, xzj8b3, zhelezov, zpytela |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:bcbdd326b2fbbaa7d37c1200b991217a36ee36fcd7546fb7e30e079268a793ac;VARIANT_ID=matecompiz; | ||
Fixed In Version: | selinux-policy-3.14.2-47.fc29 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-01-21 12:56:38 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
flaviohenriquedesousaribeiro
2018-11-12 16:06:15 UTC
Description of problem: Defauth Version-Release number of selected component: selinux-policy-3.14.2-42.fc29.noarch Additional info: reporter: libreport-2.9.6 hashmarkername: setroubleshoot kernel: 4.19.2-301.fc29.x86_64 type: libreport Description of problem: I rebooted the system Version-Release number of selected component: selinux-policy-3.14.2-42.fc29.noarch Additional info: reporter: libreport-2.9.6 hashmarkername: setroubleshoot kernel: 4.19.3-300.fc29.x86_64 type: libreport Description of problem: after normal system upgrade Version-Release number of selected component: selinux-policy-3.14.2-42.fc29.noarch Additional info: reporter: libreport-2.9.6 hashmarkername: setroubleshoot kernel: 4.19.5-300.fc29.x86_64 type: libreport Description of problem: Defaulth Version-Release number of selected component: selinux-policy-3.14.2-42.fc29.noarch Additional info: reporter: libreport-2.9.6 hashmarkername: setroubleshoot kernel: 4.19.5-300.fc29.x86_64 type: libreport Happens to me too on every boot.
The proposed solution, to run restorecon on /sys/firmware/efi/efivars, doesn't have any effect. The type stays unchanged: efivarfs_t. What I did to silence the warning was to build and install a module:
> sudo ausearch -m avc -c plymouthd | audit2allow -M my-plymouthd
> sudo semodule -i my-plymouthd.pp
> cat my-plymouthd.te
module my-plymouthd 1.0;
require {
type efivarfs_t;
type plymouthd_t;
class dir getattr;
}
#============= plymouthd_t ==============
allow plymouthd_t efivarfs_t:dir getattr;
commit 1ee051722534b475f7de087a9df4b95a7097acd6 (HEAD -> rawhide) Author: Lukas Vrabec <lvrabec> Date: Wed Dec 12 13:13:24 2018 +0100 Add filecontext to /sys/firmware/efi directory efivarfs_t BZ(1648978) commit f9a2d9e41edb803360694ed505de1fad58cc188c (HEAD -> rawhide) Author: Lukas Vrabec <lvrabec> Date: Wed Dec 12 13:17:29 2018 +0100 Add efivarfs_t domain to filesystem_type attribute Description of problem: Not sure when it started happening exactly, I don't reboot very often. Version-Release number of selected component: selinux-policy-3.14.2-44.fc29.noarch Additional info: reporter: libreport-2.9.7 hashmarkername: setroubleshoot kernel: 4.19.4-300.fc29.x86_64 type: libreport Is this error benign? It's the only problem I see when I look though my logs after trying to shut down and it stalls and I have to do a hard reset every time. *** Bug 1662191 has been marked as a duplicate of this bug. *** *** Bug 1662579 has been marked as a duplicate of this bug. *** (In reply to Vladimir Zhelezov from comment #5) > Happens to me too on every boot. > > The proposed solution, to run restorecon on /sys/firmware/efi/efivars, > doesn't have any effect. The type stays unchanged: efivarfs_t. What I did to > silence the warning was to build and install a module: > It is a ram-disk file system so no point in fixing the labels. Description of problem: appears by itself at logon Version-Release number of selected component: selinux-policy-3.14.2-44.fc29.noarch Additional info: reporter: libreport-2.9.7 hashmarkername: setroubleshoot kernel: 4.20.0-1.fc30.x86_64 type: libreport *** Bug 1662595 has been marked as a duplicate of this bug. *** selinux-policy-3.14.2-46.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-6a20cfef61 selinux-policy-3.14.2-46.fc29 has been pushed to the Fedora 29 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-2019-6a20cfef61 *** This bug has been marked as a duplicate of bug 1664143 *** selinux-policy-3.14.2-46.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. Description of problem: Happens during boot. Version-Release number of selected component: selinux-policy-3.14.2-44.fc29.noarch Additional info: reporter: libreport-2.9.7 hashmarkername: setroubleshoot kernel: 4.19.14-300.fc29.x86_64 type: libreport Sorry, but selinux-policy-3.14.2-46.fc29 doesn't fix this bug. I have it installed and I've just encountered this AVC alert: type=AVC msg=audit(1547557690.092:2152): avc: denied { getattr } for pid=7693 comm="plymouthd" path="/sys/firmware/efi/efivars" dev="efivarfs" ino=13962 scontext=system_u:system_r:plymouthd_t:s0 tcontext=system_u:object_r:efivarfs_t:s0 tclass=dir permissive=0 type=AVC msg=audit(1547808645.502:878): avc: denied { getattr } for pid=21774 comm="plymouthd" path="/sys/firmware/efi/efivars" dev="efivarfs" ino=205 scontext=system_u:system_r:plymouthd_t:s0 tcontext=system_u:object_r:efivarfs_t:s0 tclass=dir permissive=0 (In reply to Dominik 'Rathann' Mierzejewski from comment #19) > Sorry, but selinux-policy-3.14.2-46.fc29 doesn't fix this bug. I have it > installed and I've just encountered this AVC alert: > > type=AVC msg=audit(1547557690.092:2152): avc: denied { getattr } for > pid=7693 comm="plymouthd" path="/sys/firmware/efi/efivars" dev="efivarfs" > ino=13962 scontext=system_u:system_r:plymouthd_t:s0 > tcontext=system_u:object_r:efivarfs_t:s0 tclass=dir permissive=0 > type=AVC msg=audit(1547808645.502:878): avc: denied { getattr } for > pid=21774 comm="plymouthd" path="/sys/firmware/efi/efivars" dev="efivarfs" > ino=205 scontext=system_u:system_r:plymouthd_t:s0 > tcontext=system_u:object_r:efivarfs_t:s0 tclass=dir permissive=0 These occurred on Tue Jan 15 14:08:10 2019 and Fri Jan 18 11:50:45 2019. Was that before or after the upgrade? date -d @1547557690 Tue 15 Jan 14:08:10 CET 2019 date -d @1547808645 Fri 18 Jan 11:50:45 CET 2019 I updated selinux-policy-3.14.2-46.fc29 (from updates-testing) on 2019-01-14 at 18:50 CET, so both did occur after the upgrade. $ sudo dnf history list selinux-policy | head -n 3 ID | Command line | Date and time | Action(s) | Altered ------------------------------------------------------------------------------- 1627 | --enablerepo=updates-tes | 2019-01-14 18:50 | E, I, U | 23 E< $ sudo dnf history info 1627 | grep selinux-policy Upgrade selinux-policy-3.14.2-46.fc29.noarch @updates-testing Upgraded selinux-policy-3.14.2-44.fc29.noarch @@System Upgrade selinux-policy-targeted-3.14.2-46.fc29.noarch @updates-testing Upgraded selinux-policy-targeted-3.14.2-44.fc29.noarch @@System I'm not sure if running kernel version has anything do with it, but I was running 4.19.13 and .14 at the time: $ last reboot | head -n 3 reboot system boot 4.19.15-300.fc29 Fri Jan 18 11:51 still running reboot system boot 4.19.14-300.fc29 Tue Jan 15 14:10 - 11:50 (2+21:40) reboot system boot 4.19.13-300.fc29 Fri Jan 4 11:34 - 14:09 (11+02:34) Meanwhile selinux-policy-3.14.2-47.fc29.noarch is the current version. Hi, I tried this on my system with the latest selinux-policy build: # sesearch -A -s plymouthd_t -t efivarfs_t -c dir allow plymouthd_t efivarfs_t:dir { getattr open search }; # rpm -q selinux-policy selinux-policy-3.14.2-47.fc29.noarch #============= plymouthd_t ============== #!!!! This avc is allowed in the current policy allow plymouthd_t efivarfs_t:dir getattr; So, I'm closing this as current release. |