All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Usama Arif <usama.arif@linux.dev>, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Dave Chinner <david@fromorbit.com>, Qi Zheng <qi.zheng@linux.dev>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Muchun Song <muchun.song@linux.dev>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Kairui Song <kasong@tencent.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/shrinker: fix bogus set_shrinker_bit() with cgroup.memory=nokmem
Date: Wed, 2 Sep 2026 19:44:23 +0800	[thread overview]
Message-ID: <2def1a1a-cb47-4435-bc8a-e787672022ae@linux.dev> (raw)
In-Reply-To: <5753d853-df04-4918-9852-c23842c66428@linux.dev>


on 9/2/26 7:34 PM, Usama Arif wrote:
>
> On 02/09/2026 08:37, Jiayuan Chen wrote:
>> With cgroup.memory=nokmem, shrinker_memcg_alloc() bails out early and
>> never allocates an id, so shrinker->id keeps the 0 it got from the
>> kzalloc() in shrinker_alloc(). __list_lru_init() then copies that 0
>> into lru->shrinker_id, where it looks like a valid bit index.
>>
>> Nothing calls expand_shrinker_info() on nokmem either, so
>> shrinker_nr_max stays 0 and every memcg ends up with an empty map
>> (map_nr_max == 0).
>>
>> deferred_split_folio() hands a real memcg to __list_lru_add()
>> regardless of whether the lru is memcg aware, so the first THP queued
>> in a cgroup does set_shrinker_bit(memcg, nid, 0) and trips the bounds
>> check:
>>
>> WARNING: mm/shrinker.c:212 at set_shrinker_bit+0x7d/0x90, CPU#126
>> Call Trace:
>>   <TASK>
>>   deferred_split_folio+0x18c/0x220
>>   map_anon_folio_pmd_nopf+0xdd/0x130
>>   map_anon_folio_pmd_pf+0x14/0xb0
>>   do_huge_pmd_anonymous_page+0x1a1/0x620
>>   __handle_mm_fault+0xea9/0x10d0
>>   handle_mm_fault+0xe5/0x320
>>   do_user_addr_fault+0x1cc/0x870
>>   exc_page_fault+0x81/0x1b0
>>   asm_exc_page_fault+0x27/0x30
>>   </TASK>
>>
>> Harmless, the WARN_ON_ONCE() is what keeps the out of bounds unit[]
>> read from happening, but the id should not look valid in the first
>> place. Clear it before returning.
>>
>> Two other spots could paper over this: drop the id in
>> __list_lru_init() when nokmem turns memcg_aware off, or make
>> deferred_split_folio() pass NULL like list_lru_add_obj() does. Both
>> leave shrinker->id lying around for the next caller, so fix it where
>> the id is handed out.
>>
>> Fixes: fafaeceb89a5 ("mm: switch deferred split shrinker to list_lru")
>> Signed-off-by: Jiayuan Chen <jiayuan.chen@linux.dev>
>> ---
>>   mm/shrinker.c | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/mm/shrinker.c b/mm/shrinker.c
>> index a70aab124a0e..7ec2a9704f6f 100644
>> --- a/mm/shrinker.c
>> +++ b/mm/shrinker.c
>> @@ -227,6 +227,8 @@ static int shrinker_memcg_alloc(struct shrinker *shrinker)
>>   {
>>   	int id;
>>   
>> +	shrinker->id = -1;
>> +
>>   	if (mem_cgroup_disabled())
>>   		return -ENOSYS;
>>   	if (mem_cgroup_kmem_disabled() && !(shrinker->flags & SHRINKER_NONSLAB))
>
> Thanks for the fix!
>
> I think the initialization would look better in shrinker_alloc()?


Well, we have to add macro if we move it to shrinker_alloc()


     shrinker->flags = flags | SHRINKER_ALLOCATED;
     shrinker->seeks = DEFAULT_SEEKS;

+#ifdef CONFIG_MEMCG
+        shrinker->id = -1;
+#endif


No strong preference for me :)



  reply	other threads:[~2026-09-02 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02  7:37 [PATCH] mm/shrinker: fix bogus set_shrinker_bit() with cgroup.memory=nokmem Jiayuan Chen
2026-09-02 11:34 ` Usama Arif
2026-09-02 11:44   ` Jiayuan Chen [this message]
2026-09-02 15:40 ` Shakeel Butt

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=2def1a1a-cb47-4435-bc8a-e787672022ae@linux.dev \
    --to=jiayuan.chen@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=hannes@cmpxchg.org \
    --cc=kasong@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=qi.zheng@linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeel.butt@linux.dev \
    --cc=usama.arif@linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.