linux-kernel - Re: [PATCH -next] cgroup: increase maximum subsystem count from 16 to 32

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: <1f31d8d2-811d-4dff-b036-2eb201f623ba@huaweicloud.com>
Date: Sat, 31 Jan 2026 11:00:05 +0800
From: Chen Ridong <chenridong@...weicloud.com>
To: Michal Koutný <mkoutny@...e.com>
Cc: tj@...nel.org, hannes@...xchg.org, rostedt@...dmis.org,
 mhiramat@...nel.org, mathieu.desnoyers@...icios.com, inwardvessel@...il.com,
 shakeel.butt@...ux.dev, cgroups@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
 lujialin4@...wei.com
Subject: Re: [PATCH -next] cgroup: increase maximum subsystem count from 16 to
 32



On 2026/1/30 18:22, Michal Koutný wrote:
> On Thu, Jan 29, 2026 at 05:51:33PM +0800, Chen Ridong <chenridong@...weicloud.com> wrote:
>> We compiled with 'make allmodconfig'.
> 
> A-ha.
> 
>> The BUILD_BUG_ON(CGROUP_SUBSYS_COUNT > 16) macro worked correctly.
> 
> Good.
> 
>> Can I propose increasing the maximum number now? If we switch certain configs to
>> default N and then a new subsystem is added later, the default configuration may
>> work fine, but it will become a problem under allmodconfig — which some users
>> actually rely on.
>>
>> Besides, this shouldn't be a major change, right?
> 
> I'd like there to be gradual move away from legacy controllers code
> captured in config defaults.
> Could you adjust the commit message to stress out the allmodconfig tests?
> 

Sure, will update.

-- 
Best regards,
Ridong