linux-kernel - Re: [PATCH v2 1/2] cgroup: Add a hint to allow v1 controller to use v2 behavior

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: <bbc17fa5-3321-39a0-a98b-b57ed0381fb9@redhat.com>
Date:   Thu, 17 Aug 2017 14:56:03 -0400
From:   Waiman Long <longman@...hat.com>
To:     Tejun Heo <tj@...nel.org>
Cc:     Li Zefan <lizefan@...wei.com>,
        Johannes Weiner <hannes@...xchg.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] cgroup: Add a hint to allow v1 controller to use
 v2 behavior

On 08/17/2017 02:48 PM, Tejun Heo wrote:
> Hello, Waiman.
>
> On Thu, Aug 17, 2017 at 02:25:38PM -0400, Waiman Long wrote:
>> For some cgroup controllers, the behavior on cgroup v1 differs somewhat
>> from cgroup v2. To indicate that a controller can use v2 behavior
>> in cgroup v1, a new cgroupfs mount option "v2_mode" is added. This
>> is essentially a hint, there is no obligation for a controller to
>> comply with this semantics.
> Heh, I don't think we can make it a generic flag.  We can't have one
> kernel interpreting the option one way and later kernels doing
> differently.  Let's just make it cpuset specific - something like
> cpuset_v2_mode.
>
> Thanks.
>
That is fine for me. I will update the patchset accordingly.

Thanks,
Longman