Linux Trace Kernel
 help / color / mirror / Atom feed
From: Chen Ridong <chenridong@huaweicloud.com>
To: tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com,
	rostedt@goodmis.org, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com, inwardvessel@gmail.com,
	shakeel.butt@linux.dev
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org, lujialin4@huawei.com
Subject: Re: [PATCH -next] cgroup: increase maximum subsystem count from 16 to 32
Date: Thu, 29 Jan 2026 15:22:49 +0800	[thread overview]
Message-ID: <026a6cd3-1b77-430f-9c4e-8ea0782ed94c@huaweicloud.com> (raw)
In-Reply-To: <20260129063133.209874-1-chenridong@huaweicloud.com>



On 2026/1/29 14:31, Chen Ridong wrote:
> The current cgroup subsystem limit of 16 is insufficient, as the number of
> subsystems has already reached this maximum. Attempting to add new
> subsystems beyond this limit results in boot failures.

We found this issue because our product includes a subsystem not present in the
community version, causing the total number of subsystems to exceed 16. When all
subsystems are enabled, the system fails to boot.

-- 
Best regards,
Ridong


  reply	other threads:[~2026-01-29  7:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29  6:31 [PATCH -next] cgroup: increase maximum subsystem count from 16 to 32 Chen Ridong
2026-01-29  7:22 ` Chen Ridong [this message]
2026-01-29  9:23 ` Michal Koutný
2026-01-29  9:51   ` Chen Ridong
2026-01-29 18:33     ` Waiman Long
2026-01-30  0:41       ` Chen Ridong
2026-01-30 10:22     ` Michal Koutný
2026-01-31  3:00       ` Chen Ridong
2026-01-30  1:24 ` JP Kobryn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=026a6cd3-1b77-430f-9c4e-8ea0782ed94c@huaweicloud.com \
    --to=chenridong@huaweicloud.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=inwardvessel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lujialin4@huawei.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=mkoutny@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=shakeel.butt@linux.dev \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox