From: Tejun Heo <tj@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: "Andy Lutomirski" <luto@amacapital.net>,
"Alexei Starovoitov" <alexei.starovoitov@gmail.com>,
"Andy Lutomirski" <luto@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Daniel Mack" <daniel@zonque.org>,
"David S. Miller" <davem@davemloft.net>,
kafai@fb.com, "Florian Westphal" <fw@strlen.de>,
"Harald Hoyer" <harald@redhat.com>,
"Network Development" <netdev@vger.kernel.org>,
"Sargun Dhillon" <sargun@sargun.me>,
"Pablo Neira Ayuso" <pablo@netfilter.org>,
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>,
"Linux API" <linux-api@vger.kernel.org>
Subject: Re: [RESEND][PATCH v4] cgroup: Use CAP_SYS_RESOURCE to allow a process to migrate other tasks between cgroups
Date: Fri, 9 Dec 2016 08:27:21 -0500 [thread overview]
Message-ID: <20161209132721.GA30394@mtj.duckdns.org> (raw)
In-Reply-To: <CALAqxLUkqSAEiHE038w+ZGUmhPgj2SpG7BLcPrrtU46VYcO=KA@mail.gmail.com>
Hello, John.
On Thu, Dec 08, 2016 at 09:39:38PM -0800, John Stultz wrote:
> So just to clarify the discussion for my purposes and make sure I
> understood, per-cgroup CAP rules was not desired, and instead we
> should either utilize an existing cap (are there still objections to
> CAP_SYS_RESOURCE? - this isn't clear to me) or create a new one (ie,
> bring back the older CAP_CGROUP_MIGRATE patch).
Let's create a new one. It looks to be a bit too different to share
with an existing one.
> Tejun: Do you have a more finished version of your patch that I should
> add my changes on top of?
Oh, just submit the patch on top of the current for-next. I can queue
mine on top of yours. They are mostly orthogonal.
Thanks.
--
tejun
prev parent reply other threads:[~2016-12-09 13:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 23:28 [RESEND][PATCH v4] cgroup: Use CAP_SYS_RESOURCE to allow a process to migrate other tasks between cgroups John Stultz
2016-11-08 23:41 ` Kees Cook
2016-11-08 23:51 ` Andy Lutomirski
2016-11-09 0:03 ` Alexei Starovoitov
2016-11-09 0:12 ` Andy Lutomirski
2016-11-23 0:57 ` John Stultz
2016-12-06 0:28 ` John Stultz
2016-12-06 0:36 ` Andy Lutomirski
2016-12-06 2:00 ` Serge E. Hallyn
2016-12-06 16:57 ` Tejun Heo
2016-12-06 16:55 ` Tejun Heo
2016-12-06 17:01 ` Andy Lutomirski
2016-12-06 18:12 ` Tejun Heo
2016-12-06 18:13 ` Andy Lutomirski
2016-12-06 18:23 ` Tejun Heo
2016-12-09 5:39 ` John Stultz
2016-12-09 13:27 ` Tejun Heo [this message]
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=20161209132721.GA30394@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=amit.pundir@linaro.org \
--cc=ccross@android.com \
--cc=cgroups@vger.kernel.org \
--cc=christian.potzsch@imgtec.com \
--cc=corbet@lwn.net \
--cc=daniel@zonque.org \
--cc=davem@davemloft.net \
--cc=dimitrysh@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=fw@strlen.de \
--cc=harald@redhat.com \
--cc=john.stultz@linaro.org \
--cc=kafai@fb.com \
--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=luto@kernel.org \
--cc=mic@digikod.net \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=romlem@android.com \
--cc=sargun@sargun.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox