linux-kernel - Re: [lxc-devel] [RFC PATCH] cgroup, cpuset: add cpuset.remap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170831135022.GA1599492@devbig577.frc2.facebook.com>
Date:   Thu, 31 Aug 2017 06:50:22 -0700
From:   Tejun Heo <tj@...nel.org>
To:     Christian Brauner <christian.brauner@...onical.com>
Cc:     christian.brauner@...ntu.com, Li Zefan <lizefan@...wei.com>,
        cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
        w.bumiller@...xmox.com, stgraber@...ntu.com, serge@...lyn.com
Subject: Re: [lxc-devel] [RFC PATCH] cgroup, cpuset: add cpuset.remap_cpus

On Thu, Aug 31, 2017 at 11:41:47AM +0200, Christian Brauner wrote:
> On Wed, Aug 30, 2017 at 05:41:31PM -0700, Tejun Heo wrote:
> > Hello,
> > 
> > On Wed, Aug 30, 2017 at 03:27:55PM +0200, Christian Brauner wrote:
> > > The following patch was sent a while back by Wolfgang Bumiller to remap cpusets
> > > for a whole subtree in a cgroup v1 cpuset hierarchy. The fact that currently
> > > this is not possible in a non-racy why is a pretty big limitation. This is
> > > especially true for nested containers. Where the nested containers often create
> > > additional subcgroups in the cpuset controller at will. The fact that you can't
> > > *easily* and in a non-racy way tighten the restriction on them after having
> > > created the parent container's cpuset cgroup seems really troubling.
> > 
> > There was a recent patch to enable v2 behavior on v1, which feels like
> > the better approach at this point.  I'm not sure about adding a whole
> > new interface for this.
> 
> Cool. If it can be done easier and less invasive I'm all for it. Did the patch
> already make it into your branch and - only if you happen to have the reference
> flying around - could you point me to it.

https://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git/commit/?h=for-4.14&id=b8d1b8ee93df8ffbabbeadd65d39853cfad6d698

Thanks.

-- 
tejun