Bug 1027148
Summary: | avc: denied { setattr } for pid=183 comm="systemd-tmpfile" during boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Vitaly Kuznetsov <vkuznets> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 20 | CC: | atodorov, dominick.grift, dwalsh, johannbg, keramidasceid, lemenkov, lnykryn, lvrabec, mgrepl, msekleta, plautrba, systemd-maint, vpavlin, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.12.1-122.fc20 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-02-12 14:44:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Vitaly Kuznetsov
2013-11-06 09:39:24 UTC
I can also see: Nov 6 09:19:40 ip-10-62-83-156 systemd-tmpfiles: chmod(/var/log/journal) failed: Permission denied Nov 6 09:19:40 ip-10-62-83-156 systemd-tmpfiles: chmod(/var/log/journal/7bd3c66a3d974c51b7a407a5bd3073b9) failed: Permission denied in /var/log/messages Confirm that. I have to add the following rule: https://github.com/lemenkov/selinux-rules/blob/master/auriga-systemd-tmpfiles.te module auriga-systemd-tmpfiles 1.0; require { type systemd_tmpfiles_t; type var_log_t; class dir { relabelfrom relabelto setattr }; } #============= systemd_tmpfiles_t ============== allow systemd_tmpfiles_t var_log_t:dir { relabelfrom relabelto setattr }; Hm, I get a slightly simpler result from audit2allow: #============= systemd_tmpfiles_t ============== allow systemd_tmpfiles_t var_log_t:dir setattr; Either way, can we get this applied? This results in an annoying warning for probably all F20 installations? systemd changed in http://cgit.freedesktop.org/systemd/systemd/commit/?id=4608af43. Seen here: http://beaker.fedoraproject.org/bkr/jobs/51 will re-test with the latest. Looks like the latest code in F20 allows this. selinux-policy-3.12.1-120.fc20 or earlier. selinux-policy-3.12.1-121.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-121.fc20 Package selinux-policy-3.12.1-121.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-121.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-1700/selinux-policy-3.12.1-121.fc20 then log in and leave karma (feedback). Package selinux-policy-3.12.1-122.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-122.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-1700/selinux-policy-3.12.1-122.fc20 then log in and leave karma (feedback). selinux-policy-3.12.1-122.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |