| Summary: | crond AVC msgs | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Miroslav Grepl <mgrepl> |
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | dwalsh, lpoetter, mgrepl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-02 13:51:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Well, probably relates with
> just wanted to let everybody know that I reverted the logic in
> pam_sytemd which automatically creates a cgroup in the 'cpu' hierarchy
> for every user/session, since it makes it impossible to use RT
> scheduling from user/session processes then.
Seems like something we should allow., I believe we want to allow cron to setup the cgroups before launching a job for a user. Fixed in selinux-policy-3.9.13-9.fc15. |
I am seeing on Rawhide with # semodule -d unconfined in permissive mode AVC msgs like these type=AVC msg=audit(1296644461.791:190): avc: denied { write } for pid=4435 comm="crond" name="user" dev=cgroup ino=21207 scontext=system_u:system_r:crond_t:s0-s0:c0.c1023 tcontext=system_u:object_r:cgroup_t:s0 tclass=dir ---- time->Wed Feb 2 12:01:01 2011 type=PATH msg=audit(1296644461.792:191): item=0 name="/sys/fs/cgroup/systemd/user/root/5/tasks" inode=63024 dev=00:13 mode=0100644 ouid=0 ogid=0 rdev=00:00 obj=system_u:object_r:cgroup_t:s0 type=AVC msg=audit(1296644461.790:185): avc: denied { getattr } for pid=4435 comm="crond" path="/var/run/user" dev=tmpfs ino=12597 scontext=system_u:system_r:crond_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_auth_t:s0 tclass=dir ---- time->Wed Feb 2 12:01:01 2011 type=PATH msg=audit(1296644461.790:186): item=0 name="/var/run/user/.pam-systemd-lock" inode=21204 dev=00:23 mode=0100600 ouid=0 ogid=500 rdev=00:00 obj=system_u:object_r:var_auth_t:s0 ------------- allow crond_t cgroup_t:dir { write rmdir setattr read remove_name create add_name }; allow crond_t cgroup_t:file { write read getattr open setattr }; allow crond_t var_auth_t:dir { search setattr read create write getattr rmdir remove_name open add_name }; allow crond_t var_auth_t:file { read write open lock }; ------------ The log is attached. Is this something new?