From: SeongJae Park <sj@kernel.org>
To: Xiu Jianfeng <xiujianfeng@huawei.com>
Cc: SeongJae Park <sj@kernel.org>,
tj@kernel.org, lizefan.x@bytedance.com, hannes@cmpxchg.org,
akpm@linux-foundation.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
m.szyprowski@samsung.com
Subject: Re: [PATCH v3 -next] mm/hugetlb_cgroup: register lockdep key for cftype
Date: Wed, 19 Jun 2024 09:29:10 -0700 [thread overview]
Message-ID: <20240619162910.106034-1-sj@kernel.org> (raw)
In-Reply-To: <20240619015527.2212698-1-xiujianfeng@huawei.com>
On Wed, 19 Jun 2024 01:55:27 +0000 Xiu Jianfeng <xiujianfeng@huawei.com> wrote:
> When CONFIG_DEBUG_LOCK_ALLOC is enabled, the following commands can
> trigger a bug,
>
> mount -t cgroup2 none /sys/fs/cgroup
> cd /sys/fs/cgroup
> echo "+hugetlb" > cgroup.subtree_control
[...]
>
> Fixes: e18df2889ff9 ("mm/hugetlb_cgroup: prepare cftypes based on template")
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Closes: https://lore.kernel.org/oe-lkp/202406181046.8d8b2492-oliver.sang@intel.com
> Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com>
>
> ---
> v3: remove #ifdef CONFIG_DEBUG_LOCK_ALLOC in struct cftype
I confirmed the issue is fixed.
Tested-by: SeongJae Park <sj@kernel.org>
Closes: https://lore.kernel.org/20240618233608.400367-1-sj@kernel.org
[...]
Thanks,
SJ
prev parent reply other threads:[~2024-06-19 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240619020518eucas1p17fb54c2c1cb9c62f1cc5bf9b04c1ec19@eucas1p1.samsung.com>
2024-06-19 1:55 ` Xiu Jianfeng
2024-06-19 15:17 ` Marek Szyprowski
2024-06-19 16:29 ` SeongJae Park [this message]
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=20240619162910.106034-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan.x@bytedance.com \
--cc=m.szyprowski@samsung.com \
--cc=tj@kernel.org \
--cc=xiujianfeng@huawei.com \
/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