mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Aleksa Sarai <asarai@suse.de>
Cc: Li Zefan <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	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: Fri, 20 May 2016 08:22:44 -0700	[thread overview]
Message-ID: <20160520152244.GB5632@htj.duckdns.org> (raw)
In-Reply-To: <573F23D0.2030500@suse.de>

On Sat, May 21, 2016 at 12:48:48AM +1000, Aleksa Sarai wrote:
> Are there any comments on this version of the patchset? I thought we had
> reached an agreement that the underlying feature (allowing a process to
> manage its own cgroups) was useful. Is there a better way of solving this
> problem, that I don't know of?

I still don't see why this is necessary.  Delegation is done through
chmodding.  There's no reason to deviate for namespaces.

Thanks.

-- 
tejun

  reply	other threads:[~2016-05-20 15:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-14  3:19 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 [this message]
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
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=20160520152244.GB5632@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=asarai@suse.de \
    --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 \
    /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
all inboxes | Powered by JetHome®