From: Qi Zheng <qi.zheng@linux.dev>
To: akpm@linux-foundation.org, hughd@google.com,
baolin.wang@linux.alibaba.com, usama.arif@linux.dev,
yi1.lai@intel.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Qi Zheng <zhengqi.arch@bytedance.com>
Subject: [PATCH] mm: shmem: assign a lock class to the unused huge shrinklist
Date: Sun, 11 Oct 2026 12:59:56 +0800 [thread overview]
Message-ID: <20261011045956.30277-1-qi.zheng@linux.dev> (raw)
In-Reply-To: <20261010161622.3a460fdbcd6765adb5c1eb7f@linux-foundation.org>
From: Qi Zheng <zhengqi.arch@bytedance.com>
The unused huge shrinklist shares the default list_lru lock class with the
dentry LRU. Although they use distinct lock instances, lockdep conflates
their dependencies and reports a circular locking dependency:
WARNING: possible circular locking dependency detected
Give the unused huge shrinklist a dedicated lock class to fix this
false-positive lockdep warning.
Fixes: b9b1861d4f7a ("mm: shmem: make unused huge shrinker memcg aware")
Reported-by: kernel test robot <yi1.lai@intel.com>
Closes: https://lore.kernel.org/oe-lkp/202610091403.d1d8080b-lkp@intel.com
Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
---
mm/shmem.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/mm/shmem.c b/mm/shmem.c
index 5a9bcc7c66926..a6e3c9c7f72da 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -5164,6 +5164,9 @@ static const struct dentry_operations shmem_ci_dentry_ops = {
static int shmem_fill_super(struct super_block *sb, struct fs_context *fc)
{
+#ifdef CONFIG_TRANSPARENT_HUGEPAGE
+ static struct lock_class_key shmem_unused_huge_lock_key;
+#endif
struct shmem_options *ctx = fc->fs_private;
struct inode *inode;
struct shmem_sb_info *sbinfo;
@@ -5243,7 +5246,8 @@ static int shmem_fill_super(struct super_block *sb, struct fs_context *fc)
goto failed;
#ifdef CONFIG_TRANSPARENT_HUGEPAGE
- if (list_lru_init_memcg(&sbinfo->shrinklist, sb->s_shrink))
+ if (list_lru_init_memcg_key(&sbinfo->shrinklist, sb->s_shrink,
+ &shmem_unused_huge_lock_key))
goto failed;
#endif
--
2.54.0
parent reply other threads:[~2026-10-11 5:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20261010161622.3a460fdbcd6765adb5c1eb7f@linux-foundation.org>]
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=20261011045956.30277-1-qi.zheng@linux.dev \
--to=qi.zheng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=usama.arif@linux.dev \
--cc=yi1.lai@intel.com \
--cc=zhengqi.arch@bytedance.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
all inboxes | Powered by JetHome®