Bug 446203 - Control group (cgroup) support
Summary: Control group (cgroup) support
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-13 14:29 UTC by Michal Schmidt
Modified: 2008-07-02 19:36 UTC (History)
1 user (show)

Fixed In Version: 72
Clone Of:
Environment:
Last Closed: 2008-07-02 19:36:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
use genconfs for cgroup (599 bytes, patch)
2008-05-13 14:29 UTC, Michal Schmidt
no flags Details | Diff

Description Michal Schmidt 2008-05-13 14:29:24 UTC
Description of problem:
Peter Zijlstra pointed out to me that the control group kernel feature is not
supported by the SELinux policy. Files in a mounted cgroup filesystem are
unlabeled and the administrator is prevented by SELinux to create a new control
group.


Version-Release number of selected component (if applicable):
selinux-policy-3.3.1-49.fc9
kernel-2.6.25-14.fc9.x86_64

How reproducible:
100%

Steps to Reproduce:
mkdir /dev/cgroup
mount -t cgroup cpu /dev/cgroup
ls -lZ /dev/cgroup
mkdir /dev/cgroup/my_cool_new_group
  
Actual results:
The files have the type unlabeled_t and an AVC denial is generated:
host=leela type=AVC msg=audit(1210681905.593:30): avc: denied { associate } for
pid=1055 comm="mkdir" name="my_cool_new_group"
scontext=unconfined_u:object_r:unlabeled_t:s0
tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem 

Expected results:
The filesystem should be labeled and new control groups should be allowed.

Additional info:
I propose the attached patch which I have tested on my system.

Comment 1 Michal Schmidt 2008-05-13 14:29:24 UTC
Created attachment 305239 [details]
use genconfs for cgroup

Comment 2 Daniel Walsh 2008-07-02 19:36:19 UTC
Fixed in selinux-policy-3.3.1-72.fc9.noarch


Note You need to log in before you can comment on or make changes to this bug.