As a heads up, this is just a first RFC and not a submission. Android currently loosens the cgroup attchment permissions, allowing tasks with CAP_SYS_NICE to be able to allow tasks to move arbitrary tasks across cgroups. At first glance, overloading CAP_SYS_NICE seems a bit hackish, but this shows that there is a active and widely deployed use for different cgroup attachment rules then what is currently available. I've tried to rework the patches so this attachment policy is build time configurable, and wanted to send them out for review so folks might give their thoughts on this implementation and what they might see as a better way to go about achieving the same goal. Thoughts and feedback would be appriciated! thanks -john Cc: Tejun Heo <tj@xxxxxxxxxx> Cc: Li Zefan <lizefan@xxxxxxxxxx> Cc: Jonathan Corbet <corbet@xxxxxxx> Cc: cgroups@xxxxxxxxxxxxxxx Cc: Android Kernel Team <kernel-team@xxxxxxxxxxx> Cc: Rom Lemarchand <romlem@xxxxxxxxxxx> Cc: Colin Cross <ccross@xxxxxxxxxxx> Colin Cross (1): cgroup: Add generic cgroup subsystem permission checks Rom Lemarchand (1): cgroup: Add a memcg and cpu cg allow_attach policy for Android Documentation/cgroups/cgroups.txt | 9 +++++++++ include/linux/cgroup.h | 14 ++++++++++++++ init/Kconfig | 7 +++++++ kernel/Makefile | 1 + kernel/cgroup.c | 39 ++++++++++++++++++++++++++++++++++++--- kernel/cgroup_nice_attach.c | 29 +++++++++++++++++++++++++++++ kernel/sched/core.c | 3 +++ mm/memcontrol.c | 3 +++ 8 files changed, 102 insertions(+), 3 deletions(-) create mode 100644 kernel/cgroup_nice_attach.c -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
