linux-kernel - Re: [PATCH] Documentation: cgroup: clarify controller enabling semantics

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: <aDdRAFMFY5hI2uNn@linux.ibm.com>
Date: Wed, 28 May 2025 23:38:00 +0530
From: Vishal Chourasia <vishalc@...ux.ibm.com>
To: Michal Koutný <mkoutny@...e.com>
Cc: Tejun Heo <tj@...nel.org>, Johannes Weiner <hannes@...xchg.org>,
        Jonathan Corbet <corbet@....net>, cgroups@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: cgroup: clarify controller enabling
 semantics

On Wed, May 28, 2025 at 07:05:06PM +0200, Michal Koutný wrote:
> On Wed, May 28, 2025 at 06:48:37PM +0530, Vishal Chourasia <vishalc@...ux.ibm.com> wrote:
> > The part that was confused me, was the meaning behind controller being
> > available vs. enabled in a cgroup.
> > 
> > Though, the documentation does mention what it means for a controller to
> > be enabled in a cgroup later in the text. But at the point of the
> > change it is unclear.
> 
> There's a picture [1] that may be more descriptive than the docs (on
> which it is based).
Thanks for the reference. 

I didn't get the part about "io controller enabling memory controller
too". Is it referring to the fact that multiple controller can work
together in a cgroup? Because, enabling just the io controller does not
automatically enable memory controller too.

Okay, what do you suggest, should I send out V2 taking corrections from
others?

Regards,
Vishal

> 
> HTH,
> Michal
> 
> [1] https://paste.opensuse.org/pastes/987b665209bb