From: Yosry Ahmed <yosry@kernel.org>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Usama Arif <usama.arif@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>, Zi Yan <ziy@nvidia.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Kiryl Shutsemau <kas@kernel.org>,
Dave Chinner <david@fromorbit.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: switch deferred split shrinker to list_lru
Date: Wed, 11 Mar 2026 14:59:19 -0700 [thread overview]
Message-ID: <CAO9r8zM_fY_9nqQ2YHy9xTtdsesuOdQU_LntbZk149gL0gE=Kw@mail.gmail.com> (raw)
In-Reply-To: <abHLtmDvYl5QYCv0@linux.dev>
> > Okay, lockdep actually does warn. rcu_read_lock_held() is explicit and
> > not appeased by implicit RCU sections.
> >
> > Paul pointed me to rcu_read_lock_any_held(), which we could use in
> > obj_cgroup_memcg() to suppress the splat and permit implicit RCU.
> >
> > Or we can make rcu_read_lock() explicit in the above code.
> >
> > Any preferences for how we want to handle this in MM code?
>
> I would vote for explicit rcu_read_lock() to be consistent with other places.
+1
next prev parent reply other threads:[~2026-03-11 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 15:43 Johannes Weiner
2026-03-11 15:46 ` Johannes Weiner
2026-03-11 15:49 ` David Hildenbrand (Arm)
2026-03-11 17:00 ` Usama Arif
2026-03-11 17:42 ` Johannes Weiner
2026-03-11 19:24 ` Johannes Weiner
2026-03-11 20:09 ` Shakeel Butt
2026-03-11 21:59 ` Yosry Ahmed [this message]
2026-03-11 22:23 ` Dave Chinner
2026-03-12 14:26 ` Johannes Weiner
2026-03-12 9:14 ` [syzbot ci] " syzbot ci
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='CAO9r8zM_fY_9nqQ2YHy9xTtdsesuOdQU_LntbZk149gL0gE=Kw@mail.gmail.com' \
--to=yosry@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=usama.arif@linux.dev \
--cc=ziy@nvidia.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