From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Tejun Heo <tj@kernel.org>
Cc: Aleksa Sarai <asarai@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
"Serge E. Hallyn" <serge.hallyn@ubuntu.com>,
Aditya Kali <adityakali@google.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
Christian Brauner <cbrauner@suse.de>,
dev@opencontainers.org
Subject: Re: [PATCH v1 3/3] cgroup: relax common ancestor restriction for direct descendants
Date: Thu, 21 Jul 2016 08:34:36 -0700 [thread overview]
Message-ID: <1469115276.2331.23.camel@HansenPartnership.com> (raw)
In-Reply-To: <20160721152648.GA23759@htj.duckdns.org>
On Thu, 2016-07-21 at 11:26 -0400, Tejun Heo wrote:
> Hello, James.
>
> On Thu, Jul 21, 2016 at 08:16:34AM -0700, James Bottomley wrote:
> > > That'd be one side. The other side is the one moving. Let's say
> > > the system admin thing wants to move all processe from A proper
> > > to B. It would do that by draining processes from A's procs
> > > file into B's and even that is multistep and can race.
> >
> > So the second part is that once we allow the creation of
> > subdirectories, there's no unified tasks file, so there's no way of
> > draining A proper without enumerating and descending into the
> > cgroupns created subtrees in A?
>
> Not that. If it races, it will end up moving processes which are no
> longer in A proper.
So if I as the cgroup ns owner am moving a task from A to A_subdir, the
admin scanning tasks in all of A may miss this task in motion because
all the tasks files can't be scanned atomically?
James
next prev parent reply other threads:[~2016-07-21 15:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 16:18 [PATCH v1 0/3] cgroup: allow for unprivileged management Aleksa Sarai
2016-07-18 16:18 ` [PATCH v1 1/3] kernfs: add support for custom per-sb permission hooks Aleksa Sarai
2016-07-18 16:18 ` [PATCH v1 2/3] cgroup: allow for unprivileged subtree management Aleksa Sarai
2016-07-20 15:45 ` Tejun Heo
2016-07-20 22:59 ` Aleksa Sarai
2016-07-18 16:18 ` [PATCH v1 3/3] cgroup: relax common ancestor restriction for direct descendants Aleksa Sarai
2016-07-20 15:51 ` Tejun Heo
2016-07-20 22:58 ` Aleksa Sarai
2016-07-20 23:02 ` Tejun Heo
2016-07-20 23:18 ` Aleksa Sarai
2016-07-20 23:19 ` Tejun Heo
2016-07-21 7:49 ` Aleksa Sarai
2016-07-21 14:33 ` Serge E. Hallyn
2016-07-21 14:37 ` Aleksa Sarai
2016-07-21 15:01 ` Tejun Heo
2016-07-21 15:09 ` Serge E. Hallyn
2016-07-21 14:51 ` James Bottomley
2016-07-21 14:59 ` Tejun Heo
2016-07-21 15:07 ` Aleksa Sarai
2016-07-21 15:04 ` Tejun Heo
2016-07-21 14:52 ` Tejun Heo
2016-07-21 15:04 ` James Bottomley
2016-07-21 15:07 ` Tejun Heo
2016-07-21 15:16 ` James Bottomley
2016-07-21 15:26 ` Tejun Heo
2016-07-21 15:34 ` James Bottomley [this message]
2016-07-21 15:50 ` Tejun Heo
2016-07-21 18:16 ` James Bottomley
2016-07-21 21:06 ` Tejun Heo
2016-07-22 8:30 ` Aleksa Sarai
2016-07-25 18:38 ` Tejun Heo
2016-07-25 22:54 ` Serge E. Hallyn
2016-07-22 8:24 ` Aleksa Sarai
2016-07-25 18:44 ` Tejun Heo
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=1469115276.2331.23.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=adityakali@google.com \
--cc=asarai@suse.de \
--cc=cbrauner@suse.de \
--cc=cgroups@vger.kernel.org \
--cc=chris@chris-wilson.co.uk \
--cc=dev@opencontainers.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=serge.hallyn@ubuntu.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