From: Wenyu Liu <liuwenyu.0311@bytedance.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: tj@kernel.org, hannes@cmpxchg.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org,
Wenyu Liu <liuwenyu.0311@bytedance.com>
Subject: Re: [PATCH] cgroup: Improve cgroup_addrm_files remove files handling
Date: Wed, 12 Nov 2025 10:41:41 +0800 [thread overview]
Message-ID: <be07fa50-12ce-4fb9-b2f4-445eaab220fa@bytedance.com> (raw)
In-Reply-To: <gbmz65zlanqe7p4iw6or4jqxilpv626zp4ktf6bigxs6ni2vdo@kprxb7s73qgb>
在 11/11/25 21:54, Michal Koutný 写道:
> Hi Wenyu.
>
> On Tue, Nov 11, 2025 at 09:44:27PM +0800, Wenyu Liu <liuwenyu.0311@bytedance.com> wrote:
>> Consider this situation: if we have two cftype arrays A and B
>> which contain the exact same files, and we add this two cftypes
>> with cgroup_add_cftypes().
>
> Do you have more details about this situation?
> Does this happen with any of the mainline controllers?
>
> Thanks,
> Michal
On our servers, there a kernel module that registered some control files with cpu controller(with some hacky code, finding and use cgroup_add_dfl_cftypes() via kallsyms_lookup_name()).
For some reason the module name was altered between version iterations.
And due to some accidents, unfortunately, the updated module was reloaded onto the server that previously had the old version installed, resulting in the cgroup becoming unavailable.
Not found this happenned with mainline controllers.
Thanks,
Wenyu
next prev parent reply other threads:[~2025-11-12 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 13:44 Wenyu Liu
2025-11-11 13:54 ` Michal Koutný
2025-11-12 2:41 ` Wenyu Liu [this message]
2025-11-14 15:35 ` Wenyu Liu
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=be07fa50-12ce-4fb9-b2f4-445eaab220fa@bytedance.com \
--to=liuwenyu.0311@bytedance.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--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
all inboxes | Powered by JetHome®