From: Aleksa Sarai <asarai@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Tejun Heo <tj@kernel.org>
Cc: Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Aleksa Sarai <cyphar@cyphar.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
dev@opencontainers.org
Subject: Re: [PATCH v4 0/2] cgroup: allow management of subtrees by new cgroup namespaces
Date: Sat, 21 May 2016 02:29:55 +1000 [thread overview]
Message-ID: <573F3B83.3020206@suse.de> (raw)
In-Reply-To: <1463761509.8091.19.camel@HansenPartnership.com>
>> 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/
next prev parent reply other threads:[~2016-05-20 16:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 3:19 [PATCH v4 0/2] cgroup: allow management of subtrees by new cgroup namespaces Aleksa Sarai
2016-05-14 3:19 ` [PATCH v4 1/2] cgroup: make cgroup.procs permissions userns-aware Aleksa Sarai
2016-05-14 3:20 ` [PATCH v4 2/2] cgroup: implement subtree creation on copy_cgroup_ns() Aleksa Sarai
2016-05-20 14:48 ` [PATCH v4 0/2] cgroup: allow management of subtrees by new cgroup namespaces Aleksa Sarai
2016-05-20 15:22 ` Tejun Heo
2016-05-20 15:30 ` James Bottomley
2016-05-20 16:03 ` Tejun Heo
2016-05-20 16:09 ` James Bottomley
2016-05-20 16:17 ` Tejun Heo
2016-05-20 16:25 ` James Bottomley
2016-05-20 16:29 ` Aleksa Sarai [this message]
2016-05-20 16:53 ` Tejun Heo
2016-05-20 17:28 ` James Bottomley
2016-05-20 17:49 ` Tejun Heo
2016-05-28 5:12 ` Aleksa Sarai
2016-05-31 18:18 ` Tejun Heo
2016-05-20 17:33 ` W. Trevor King
2016-05-20 17:33 ` Aditya Kali
2016-05-20 17:50 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=573F3B83.3020206@suse.de \
--to=asarai@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=cgroups@vger.kernel.org \
--cc=cyphar@cyphar.com \
--cc=dev@opencontainers.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).