Bug 955758
Summary: | systemd-readahead: failed to create shared memory segment | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Zbigniew Jędrzejewski-Szmek <zbyszek> |
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: | 19 | CC: | bugzilla, dominick.grift, dwalsh, mgrepl, systemd-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.12.1-47.fc19 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-05-30 03:32:51 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
Zbigniew Jędrzejewski-Szmek
2013-04-23 18:08:40 UTC
Avc messages? I don't see any AVC messages. Is it possible that they are not generated or logged because auditd is not yet running? auditd is initialized a while later, along with other services, while readahead is started already in the boot. Hm, after looking at it again, systemd probably might create /run/systemd by itself. It is convenient to create it in systemd-readahead, but I see that it might be inconvenient for selinux. # dmesg |grep avc # dmesg |grep avc nada Hm, I'll reboot with selinux=0 when I have acccess to the machine and see what happens. Any progress on this issue? Same problem here: [ 9.887300] systemd-readahead[267]: Failed to create /run/systemd: Permission denied [ 9.887311] systemd-readahead[267]: Failed to create shared memory segment: No such file or directory [ 9.887495] systemd-readahead[266]: Failed to create /run/systemd: Permission denied [ 9.887506] systemd-readahead[266]: Failed to create shared memory segment: No such file or directory a1cf4f67ed46cabfb111b287577be0c9b71e0672 fixes this in git. selinux-policy-3.12.1-47.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-47.fc19 Package selinux-policy-3.12.1-47.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-47.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-9565/selinux-policy-3.12.1-47.fc19 then log in and leave karma (feedback). selinux-policy-3.12.1-47.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |