All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Li Zefan <lizefan@huawei.com>, Jonathan Corbet <corbet@lwn.net>,
	"open list:CONTROL GROUP (CGROUP)" <cgroups@vger.kernel.org>,
	Android Kernel Team <kernel-team@android.com>,
	Rom Lemarchand <romlem@android.com>,
	Colin Cross <ccross@android.com>,
	Dmitry Shmidt <dimitrysh@google.com>,
	Todd Kjos <tkjos@google.com>,
	Christian Poetzsch <christian.potzsch@imgtec.com>,
	Amit Pundir <amit.pundir@linaro.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	"Serge E . Hallyn" <serge@hallyn.com>,
	Andy Lutomirski <luto@amacapital.net>,
	Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH v5] cgroup: Add new capability to allow a process to migrate other tasks between cgroups
Date: Tue, 13 Dec 2016 13:53:35 -0500	[thread overview]
Message-ID: <20161213185335.GD17672@htj.duckdns.org> (raw)
In-Reply-To: <CALAqxLU=3CC3o6Z_-bzuvtOd6=GAZBfmgbEk9P1UP==PGyJ3bg@mail.gmail.com>

On Tue, Dec 13, 2016 at 10:47:19AM -0800, John Stultz wrote:
> > Control group control?  The word control has a specific meaning for
> > cgroups and that second control doesn't make much sense to me.
> 
> But this would go against the long tradition of RAS syndrome and
> things like "struct task_struct".  :)

Well, now that you put it that way, it's starting to look good. :)
But, let's just go for CAP_CGROUP if everyone is okay with it.

Thanks.

-- 
tejun

  reply	other threads:[~2016-12-13 18:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13  1:39 [PATCH v5] cgroup: Add new capability to allow a process to migrate other tasks between cgroups John Stultz
2016-12-13  1:39 ` John Stultz
     [not found] ` <1481593143-18756-1-git-send-email-john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-12-13  1:40   ` John Stultz
2016-12-13  1:40     ` John Stultz
2016-12-13  9:47   ` Michael Kerrisk (man-pages)
2016-12-13  9:47     ` Michael Kerrisk (man-pages)
2016-12-13 16:08     ` John Stultz
     [not found]       ` <CALAqxLVz4WH5T7mjD1U5XG1pWQCJqsO2LWYcpJ+xDPjRb9QMig-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-13 18:40         ` Tejun Heo
2016-12-13 18:40           ` Tejun Heo
     [not found]           ` <20161213184057.GA17672-piEFEHQLUPpN0TnZuCh8vA@public.gmane.org>
2016-12-13 18:47             ` John Stultz
2016-12-13 18:47               ` John Stultz
2016-12-13 18:53               ` Tejun Heo [this message]
2016-12-13 16:39     ` Casey Schaufler
     [not found]       ` <221e80bd-3d99-6c35-dcd3-b2547f0abb11-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org>
2016-12-13 16:49         ` John Stultz
2016-12-13 16:49           ` John Stultz
     [not found]           ` <CALAqxLWaJT=a1Cc2Ja8ZuazjJYi3a2WW9ATB0NFP8670Dyq6bg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-13 17:17             ` Casey Schaufler
2016-12-13 17:17               ` Casey Schaufler
     [not found]               ` <f7ccb39f-bad8-4a78-c796-90927b839494-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org>
2016-12-13 17:24                 ` John Stultz
2016-12-13 17:24                   ` John Stultz
2016-12-13 17:48                   ` Casey Schaufler
2016-12-13 17:48                     ` Casey Schaufler
     [not found]                     ` <4c60e1be-c00a-5f26-f5de-7d32b9cb0f62-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org>
2016-12-13 18:13                       ` John Stultz
2016-12-13 18:13                         ` John Stultz
     [not found]                         ` <CALAqxLUbrO+vzrwgK8_yZS-uru7redOdJCAe2=yA34gwPGC2CQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-13 18:32                           ` Casey Schaufler
2016-12-13 18:32                             ` Casey Schaufler
2016-12-13 18:47                             ` 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=20161213185335.GD17672@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=amit.pundir@linaro.org \
    --cc=ccross@android.com \
    --cc=cgroups@vger.kernel.org \
    --cc=christian.potzsch@imgtec.com \
    --cc=corbet@lwn.net \
    --cc=dimitrysh@google.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=keescook@chromium.org \
    --cc=kernel-team@android.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=luto@amacapital.net \
    --cc=mtk.manpages@gmail.com \
    --cc=romlem@android.com \
    --cc=serge@hallyn.com \
    --cc=tkjos@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.