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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170831004131.GZ491396@devbig577.frc2.facebook.com>
Date:   Wed, 30 Aug 2017 17:41:31 -0700
From:   Tejun Heo <tj@...nel.org>
To:     christian.brauner@...ntu.com
Cc:     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

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.

Thanks.

-- 
tejun