Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nick Huang <sef1548@gmail.com>, Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Dave Chinner <david@fromorbit.com>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Muchun Song <muchun.song@linux.dev>,
	Qi Zheng <qi.zheng@linux.dev>,
	Meta kernel team <kernel-team@meta.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Zenghui Yu <zenghui.yu@linux.dev>, Nhat Pham <nphamcs@gmail.com>
Subject: Re: [PATCH] mm/shrinker: do not hold RCU lock in shrinker_debugfs_count_show()
Date: Tue, 25 Aug 2026 08:12:09 +0200	[thread overview]
Message-ID: <041af2b5-9136-4027-b35a-72e5044c63ab@kernel.org> (raw)
In-Reply-To: <aoxKKXjs3o6jUanE@nickhuang>

On 24/08/2026 15:42, Nick Huang wrote:
> On Wed, Jun 10, 2026 at 04:20:48PM -0700, Shakeel Butt wrote:
>> Reading the debugfs "count" file of a memcg-aware shrinker can sleep
>> inside an RCU read-side critical section:
>>
>>   BUG: sleeping function called from invalid context at kernel/cgroup/rstat.c:421
>>   RCU nest depth: 1, expected: 0
>>    css_rstat_flush
>>    mem_cgroup_flush_stats
>>    zswap_shrinker_count
>>    shrinker_debugfs_count_show
>>
>> shrinker_debugfs_count_show() invokes the ->count_objects() callback
>> under rcu_read_lock(). The zswap callback flushes memcg stats via
>> css_rstat_flush(), which may sleep, so it must not run under RCU.
>>
>> The RCU lock is not needed here. mem_cgroup_iter() takes RCU internally
>> and returns a memcg holding a css reference (dropped on the next
>> iteration or by mem_cgroup_iter_break()), so the memcg stays alive
>> without it. The shrinker is kept alive by the open debugfs file:
>> shrinker_free() removes the debugfs entries via
>> debugfs_remove_recursive(), which waits for in-flight readers to drain,
>> before call_rcu(..., shrinker_free_rcu_cb). The sibling "scan" handler
>> already invokes the sleeping ->scan_objects() callback with no RCU
>> section.
>>
>> Drop the rcu_read_lock()/rcu_read_unlock().
>>
>> Fixes: 5035ebc644ae ("mm: shrinkers: introduce debugfs interface for memory shrinkers")
>> Reported-by: Zenghui Yu <zenghui.yu@linux.dev>
>> Closes: https://lore.kernel.org/all/c052a064-cddb-494f-a0d8-f8a10b4b1c4d@linux.dev/
>> Suggested-by: Nhat Pham <nphamcs@gmail.com>
>> Signed-off-by: Shakeel Butt <shakeel.butt@linux.dev>
>> ---
>>  mm/shrinker_debug.c | 4 ----
>>  1 file changed, 4 deletions(-)
>>
>> diff --git a/mm/shrinker_debug.c b/mm/shrinker_debug.c
>> index affa64437302..cda4e86428c8 100644
>> --- a/mm/shrinker_debug.c
>> +++ b/mm/shrinker_debug.c
>> @@ -57,8 +57,6 @@ static int shrinker_debugfs_count_show(struct seq_file *m, void *v)
>>  	if (!count_per_node)
>>  		return -ENOMEM;
>>  
>> -	rcu_read_lock();
>> -
>>  	memcg_aware = shrinker->flags & SHRINKER_MEMCG_AWARE;
>>  
>>  	memcg = mem_cgroup_iter(NULL, NULL, NULL);
>> @@ -88,8 +86,6 @@ static int shrinker_debugfs_count_show(struct seq_file *m, void *v)
>>  		}
>>  	} while ((memcg = mem_cgroup_iter(NULL, memcg, NULL)) != NULL);
>>  
>> -	rcu_read_unlock();
>> -
>>  	kfree(count_per_node);
>>  	return ret;
>>  }
>> -- 
>> 2.53.0-Meta
>>
> Reviewed-by: Nick Huang <sef1548@gmail.com>

Sorry, but what exactly did you review here? In the past you were
sending AI slop:
https://lore.kernel.org/all/aeNGbNyPxJssnkbO@lucifer/

Not even properly following the process.
https://lore.kernel.org/all/20260724143408.175870-1-sef1548@gmail.com/

https://lore.kernel.org/all/?q=f%3Asef1548%40gmail.com

Why suddenly reviewing MM patches?

Best regards,
Krzysztof


  reply	other threads:[~2026-08-25  6:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 23:20 [PATCH] mm/shrinker: do not hold RCU lock in shrinker_debugfs_count_show() Shakeel Butt
2026-06-11  0:22 ` SeongJae Park
2026-06-11  0:26   ` SeongJae Park
2026-06-11  0:43     ` Shakeel Butt
2026-06-11  3:30 ` Qi Zheng
2026-06-11  6:19 ` Zenghui Yu
2026-06-11 14:35 ` Nhat Pham
2026-06-12  3:12 ` Muchun Song
2026-06-12  4:00 ` Roman Gushchin
2026-08-24 13:42 ` Nick Huang
2026-08-25  6:12   ` Krzysztof Kozlowski [this message]
2026-08-25 13:54     ` Nick Huang
2026-08-25 13:56       ` Krzysztof Kozlowski
2026-08-25 14:07         ` Nick Huang

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=041af2b5-9136-4027-b35a-72e5044c63ab@kernel.org \
    --to=krzk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=nphamcs@gmail.com \
    --cc=qi.zheng@linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=sef1548@gmail.com \
    --cc=shakeel.butt@linux.dev \
    --cc=zenghui.yu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox