From: John Stultz <john.stultz@linaro.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Tejun Heo <tj@kernel.org>, Lee Jones <lee.jones@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
cgroups mailinglist <cgroups@vger.kernel.org>,
Wei Wang <wvw@google.com>
Subject: Re: [PATCH 1/1] cgroup-v1: Grant CAP_SYS_NICE holders permission to move tasks between cgroups
Date: Mon, 4 Oct 2021 10:33:36 -0700 [thread overview]
Message-ID: <CALAqxLUE6D9aUgXQqFJ=qp3f2b6BCjHjP=Je+bo-sdX_qON+-Q@mail.gmail.com> (raw)
In-Reply-To: <CALAqxLV-tOgBMAWd36sg+bh3s0XXqKWD+P-CYgVXf7Won4auAA@mail.gmail.com>
On Mon, Oct 4, 2021 at 10:23 AM John Stultz <john.stultz@linaro.org> wrote:
> We sort of went in a big circle of creating a config time option w/
> CAP_SYS_NICE, then a new CAP_CGROUP_MIGRATE then switching to
> CAP_SYS_RESOURCE and then back to CAP_CGROUP_MIGRATE, and when that
> was panned I gave up and we kept the small patch in the Android tree
> that uses CAP_SYS_NICE.
>
> Links to previous attempts & discussion:
> v1: https://lore.kernel.org/lkml/1475556090-6278-1-git-send-email-john.stultz@linaro.org/#t
> v2: https://lore.kernel.org/lkml/1476743724-9104-1-git-send-email-john.stultz@linaro.org/
> v4: https://lore.kernel.org/lkml/1478647728-30357-1-git-send-email-john.stultz@linaro.org/
> v5: https://lore.kernel.org/lkml/1481593143-18756-1-git-send-email-john.stultz@linaro.org/
Whoops I missed one more before I gave up (CAP_CGROUP):
v6: https://lore.kernel.org/lkml/1481949827-23613-1-git-send-email-john.stultz@linaro.org/#t
prev parent reply other threads:[~2021-10-04 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 9:09 [PATCH 1/1] cgroup-v1: Grant CAP_SYS_NICE holders permission to move tasks between cgroups Lee Jones
2021-06-17 9:09 ` Lee Jones
2021-06-17 11:41 ` Tejun Heo
2021-06-17 11:41 ` Tejun Heo
2021-06-17 12:01 ` Lee Jones
2021-06-17 12:01 ` Lee Jones
2021-09-30 21:20 ` Suren Baghdasaryan
2021-09-30 21:20 ` Suren Baghdasaryan
2021-10-04 16:41 ` Tejun Heo
2021-10-04 16:41 ` Tejun Heo
2021-10-04 16:57 ` Suren Baghdasaryan
2021-10-04 16:57 ` Suren Baghdasaryan
2021-10-04 17:23 ` John Stultz
2021-10-04 17:23 ` John Stultz
2021-10-04 17:33 ` John Stultz [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='CALAqxLUE6D9aUgXQqFJ=qp3f2b6BCjHjP=Je+bo-sdX_qON+-Q@mail.gmail.com' \
--to=john.stultz@linaro.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=surenb@google.com \
--cc=tj@kernel.org \
--cc=wvw@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.