lkml.org 
[lkml]   [2016]   [May]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v4 0/2] cgroup: allow management of subtrees by new cgroup namespaces
From
Date
>>    This is stemming from the fact that an unpriv application can't
>> create its sub-cgroups without explicit delegation from the root and
>> that has always been an explicit design choice.
>> It's tied to who's responsible for cleanup afterwards and what
>> happens when the process gets migrated to a different cgroup. The
>> latter is an important issue on v1 hierarchies because migrating
>> tasks sometimes is used as a way to control resource distribution.
>
> OK, so is the only problem cleanup? If so, what if I proposed that a
> cgroup directory could only be created by the owner of the userns
> (which would be any old unprivileged user) iff they create a cgroup ns
> and the cgroup ns would be responsible for removing it again, so the
> cgroup subdirectory would be tied to the cgroup namespace as its holder
> and we'd use release of the cgroup to remove all the directories?

The only question I'd have is how would we deal with visibility (and
should a "parent" cgroup namespace be able to modify things inside the
cgroup?). And of course, how would that interact with VFS?

--
Aleksa Sarai
Software Engineer (Containers)
SUSE Linux GmbH
https://www.cyphar.com/

\
 
 \ /
  Last update: 2016-05-20 19:01    [W:0.076 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site