Bug 986647
Summary: | SELinux is preventing /usr/bin/dmesg from 'write' accesses on the file /proc/sys/kernel/printk. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Zero <HolyMaster> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | d3trax, dimer1, dominick.grift, dwalsh, g00001, henryju, HolyMaster, kisssandoradam, lanxingcan, lvrabec, mgrepl, mjs, oscar.yasu, prasanna.ven, seanbaskin |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:dafa71f88347318b34ea495b1b8985c2105e6c21e658753cb1632bf006b1429b | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-23 13:47:20 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
Zero
2013-07-21 09:02:49 UTC
What were you doing when this happened? Looks like an program is opening a write fd to /proc/sys/kernel/printk and then fork/exec dmesg? Without closeing the fd on exec. Description of problem: On Fedora 19 startup Additional info: reporter: libreport-2.1.5 hashmarkername: setroubleshoot kernel: 3.9.5-301.fc19.x86_64 type: libreport Description of problem: Alert showed on reboot after system freeze. Additional info: reporter: libreport-2.1.6 hashmarkername: setroubleshoot kernel: 3.10.11-200.fc19.x86_64 type: libreport Description of problem: Alert appeared on startup after updates applied. Additional info: reporter: libreport-2.1.7 hashmarkername: setroubleshoot kernel: 3.11.3-201.fc19.x86_64 type: libreport Can anyone tell us which app they were running when this happened? Mgrepl, we probably should just dontaudit it. Description of problem: Bumblebee: optirun glxgears -info Then Ctrl + C Additional info: reporter: libreport-2.1.7 hashmarkername: setroubleshoot kernel: 3.11.3-201.fc19.x86_64 type: libreport Description of problem: Happened on startup with newly installed kernel-3.11.4-201.fc19.x86_64. Additional info: reporter: libreport-2.1.8 hashmarkername: setroubleshoot kernel: 3.11.4-201.fc19.x86_64 type: libreport Added dontaudit for this in 9665afbaf45c4f1a525888222504159aacf98c1e in git. back ported. *** Bug 1022288 has been marked as a duplicate of this bug. *** selinux-policy-3.12.1-74.12.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-74.12.fc19 Package selinux-policy-3.12.1-74.12.fc19: * should fix your issue, * was pushed to the Fedora 19 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-74.12.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20980/selinux-policy-3.12.1-74.12.fc19 then log in and leave karma (feedback). Description of problem: Installed Bumblebee (restarted), Primus and Bumblebee-NVIDIA (restarted), then received this error message when I logged in on start up. Additional info: reporter: libreport-2.1.9 hashmarkername: setroubleshoot kernel: 3.11.7-200.fc19.x86_64 type: libreport Description of problem: Alert showed up on login after first boot with kernel-3.11.8-200.fc19.x86_64. Additional info: reporter: libreport-2.1.9 hashmarkername: setroubleshoot kernel: 3.11.8-200.fc19.x86_64 type: libreport Iẗ́'s fixed |