From: "Paul E. McKenney" <paulmck@kernel.org>
To: Bradley Morgan <brads@mainlining.org>
Cc: qiang.zhang@linux.dev, boqun@kernel.org, frederic@kernel.org,
joelagnelf@nvidia.com, linux-kernel@vger.kernel.org,
neeraj.upadhyay@kernel.org, rcu@vger.kernel.org,
urezki@gmail.com
Subject: Re: [PATCH] rcutorture: Fix suspicious rcu_dereference_check() usage for trivial-preempt
Date: Tue, 20 Oct 2026 15:01:27 -0700 [thread overview]
Message-ID: <3280ed4e-2fc0-4eef-b6b9-234bf4acce58@paulmck-laptop> (raw)
In-Reply-To: <BD9E8AED-23DC-4A7E-86E9-297B8FE29846@mainlining.org>
On Tue, Oct 20, 2026 at 04:06:49PM +0100, Bradley Morgan wrote:
> On 20 October 2026 10:49:07 BST, Zqiang <qiang.zhang@linux.dev> wrote:
> >Running the trivial-preempt flavor triggers a lockdep "suspicious RCU
> >usage" warning from rcu_torture_one_read_start():
> >
> >WARNING: suspicious RCU usage
> >kernel/rcu/rcutorture.c:2581 suspicious rcu_dereference_check() usage!
> >...
> >lockdep_rcu_suspicious
> >rcu_torture_one_read_start
> >rcu_torture_one_read
> >rcu_torture_reader
> >
> >The trivial-preempt flavor .readlock_held is set to
> >torture_readlock_not_held(),
> >which check RCU-bh/RCU-sched critical sections. however, it's read lock
> >just increments current->rcu_trivial_preempt_nesting, it's not also RCU
> >read critical sections. the rcu_dereference_check() condition is therefore
> >false, and lockdep report warnings. this commit therefore drop
> >.readlock_held
> >callback to avoid this lockdep warnings.
> >
> >Fixes: c6f4e552e1ea ("rcutorture: Add a textbook-style trivial preemptible RCU")
>
> Looks ok to me.
>
> Reviewed-by: Bradley Morgan <brads@mainlining.org>
>
> >Signed-off-by: Zqiang <qiang.zhang@linux.dev>
And it works here, thank you both. I have queued this, and thank you
Zqiang for thinking to test trivial-preempt with lockdep enabled!
Thanx, Paul
> >---
> > kernel/rcu/rcutorture.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> >diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c
> >index 92ff197f4789..1bbf8192786a 100644
> >--- a/kernel/rcu/rcutorture.c
> >+++ b/kernel/rcu/rcutorture.c
> >@@ -1164,7 +1164,6 @@ static struct rcu_torture_ops trivial_preempt_ops = {
> > .readlock = rcu_torture_read_lock_trivial_preempt,
> > .read_delay = rcu_read_delay, // just reuse rcu's version.
> > .readunlock = rcu_torture_read_unlock_trivial_preempt,
> >- .readlock_held = torture_readlock_not_held,
> > .get_gp_seq = rcu_no_completed,
> > .sync = synchronize_rcu_trivial_preempt,
> > .exp_sync = synchronize_rcu_trivial_preempt,
> >
>
> --- Thanks!
> "I'm not a very positive person" - Linus torvalds
next prev parent reply other threads:[~2026-10-20 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 9:49 Zqiang
2026-10-20 15:06 ` Bradley Morgan
2026-10-20 22:01 ` Paul E. McKenney [this message]
2026-10-20 22:03 ` Paul E. McKenney
2026-10-20 22:20 ` Joel Fernandes
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=3280ed4e-2fc0-4eef-b6b9-234bf4acce58@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=boqun@kernel.org \
--cc=brads@mainlining.org \
--cc=frederic@kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=urezki@gmail.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®