|author||Li Zefan <firstname.lastname@example.org>||2009-01-15 13:50:59 -0800|
|committer||Linus Torvalds <email@example.com>||2009-01-15 16:39:37 -0800|
cgroups: consolidate cgroup documents
Move Documentation/cpusets.txt and Documentation/controllers/* to Documentation/cgroups/ Signed-off-by: Li Zefan <firstname.lastname@example.org> Acked-by: KAMEZAWA Hiroyuki <email@example.com> Acked-by: Balbir Singh <firstname.lastname@example.org> Acked-by: Paul Menage <email@example.com> Signed-off-by: Andrew Morton <firstname.lastname@example.org> Signed-off-by: Linus Torvalds <email@example.com>
Diffstat (limited to 'Documentation/cgroups/devices.txt')
1 files changed, 52 insertions, 0 deletions
diff --git a/Documentation/cgroups/devices.txt b/Documentation/cgroups/devices.txt
new file mode 100644
@@ -0,0 +1,52 @@
+Device Whitelist Controller
+Implement a cgroup to track and enforce open and mknod restrictions
+on device files. A device cgroup associates a device access
+whitelist with each cgroup. A whitelist entry has 4 fields.
+'type' is a (all), c (char), or b (block). 'all' means it applies
+to all types and all major and minor numbers. Major and minor are
+either an integer or * for all. Access is a composition of r
+(read), w (write), and m (mknod).
+The root device cgroup starts with rwm to 'all'. A child device
+cgroup gets a copy of the parent. Administrators can then remove
+devices from the whitelist or add new entries. A child cgroup can
+never receive a device access which is denied by its parent. However
+when a device access is removed from a parent it will not also be
+removed from the child(ren).
+2. User Interface
+An entry is added using devices.allow, and removed using
+devices.deny. For instance
+ echo 'c 1:3 mr' > /cgroups/1/devices.allow
+allows cgroup 1 to read and mknod the device usually known as
+ echo a > /cgroups/1/devices.deny
+will remove the default 'a *:* rwm' entry. Doing
+ echo a > /cgroups/1/devices.allow
+will add the 'a *:* rwm' entry to the whitelist.
+Any task can move itself between cgroups. This clearly won't
+suffice, but we can decide the best way to adequately restrict
+movement as people get some experience with this. We may just want
+to require CAP_SYS_ADMIN, which at least is a separate bit from
+CAP_MKNOD. We may want to just refuse moving to a cgroup which
+isn't a descendent of the current one. Or we may want to use
+CAP_MAC_ADMIN, since we really are trying to lock down root.
+CAP_SYS_ADMIN is needed to modify the whitelist or move another
+task to a new cgroup. (Again we'll probably want to change that).
+A cgroup may not be granted more permissions than the cgroup's