From: Joel Fernandes <joel@joelfernandes.org>
To: stable@vger.kernel.org
Cc: paulmck@kernel.org, rcu@vger.kernel.org
Subject: Please apply to v5.10 stable: 4d60b475f858 ("rcu: Prevent lockdep-RCU splats on lock acquisition/release")
Date: Thu, 29 Dec 2022 02:39:06 +0000 [thread overview]
Message-ID: <Y6z9ygSGmPNz5hfd@google.com> (raw)
Hello,
Please apply to v5.10 stable: 4d60b475f858 ("rcu: Prevent lockdep-RCU splats
on lock acquisition/release"). The patch made it in v5.11
Without it, I get the follow splat on TREE05 rcutorture testing:
[ 1.253678] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.10.162-rc1+ #6
[ 1.253678] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
[ 1.253678] Call Trace:
[ 1.253678]
[ 1.253678] =============================
[ 1.253678] WARNING: suspicious RCU usage
[ 1.253678] 5.10.162-rc1+ #6 Not tainted
[ 1.253678] -----------------------------
[ 1.253678] kernel/kprobes.c:300 RCU-list traversed in non-reader section!!
I tested with the patch and the warning is gone.
thanks,
- Joel
next reply other threads:[~2022-12-29 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 2:39 Joel Fernandes [this message]
2022-12-29 16:10 ` Please apply to v5.10 stable: 4d60b475f858 ("rcu: Prevent lockdep-RCU splats on lock acquisition/release") Joel Fernandes
2022-12-30 1:02 ` Joel Fernandes
2022-12-30 4:43 ` 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=Y6z9ygSGmPNz5hfd@google.com \
--to=joel@joelfernandes.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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