From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCH v5] cgroup: Add new capability to allow a process to migrate other tasks between cgroups Date: Tue, 13 Dec 2016 13:40:57 -0500 Message-ID: <20161213184057.GA17672@htj.duckdns.org> References: <1481593143-18756-1-git-send-email-john.stultz@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: John Stultz Cc: Michael Kerrisk , lkml , Li Zefan , Jonathan Corbet , "open list:CONTROL GROUP (CGROUP)" , Android Kernel Team , Rom Lemarchand , Colin Cross , Dmitry Shmidt , Todd Kjos , Christian Poetzsch , Amit Pundir , Dmitry Torokhov , Kees Cook , "Serge E . Hallyn" , Andy Lutomirski , Linux API List-Id: linux-api@vger.kernel.org Hello, On Tue, Dec 13, 2016 at 08:08:16AM -0800, John Stultz wrote: > On Tue, Dec 13, 2016 at 1:47 AM, Michael Kerrisk (man-pages) > wrote: > > On 13 December 2016 at 02:39, John Stultz wrote: > > So, back to the discussion of silos. I understand the argument for > > wanting a new silo. But, in that case can we at least try not to make > > it a single-use silo? > > > > How about CAP_CGROUP_CONTROL or some such, with the idea that this > > might be a capability that allows the holder to step outside usual > > cgroup rules? At the moment, that capability would allow only one such > > step, but maybe there would be others in the future. > > This sounds reasonable to me. Tejun/Andy: Objections? Control group control? The word control has a specific meaning for cgroups and that second control doesn't make much sense to me. Given how this is mostly to patch up a hole in v1's delegation model and how migration operations are different from others, I doubt that we will end up overloading it. Maybe just CAP_CGROUP? Thanks. -- tejun