From: Boqun Feng <boqun.feng@gmail.com>
To: rcu@vger.kernel.org
Cc: "Petr Mladek" <pmladek@suse.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"John Ogness" <john.ogness@linutronix.de>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Neeraj Upadhyay" <neeraj.upadhyay@kernel.org>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Josh Triplett" <josh@joshtriplett.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Uladzislau Rezki" <urezki@gmail.com>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Lai Jiangshan" <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Shuah Khan" <shuah@kernel.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Clark Williams" <clrkwllms@kernel.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Yuntao Wang" <ytcoode@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Guo Weikang" <guoweikang.kernel@gmail.com>,
"KP Singh" <kpsingh@kernel.org>,
"Huang Shijie" <shijie@os.amperecomputing.com>,
"Raul E Rangel" <rrangel@chromium.org>,
"Joel Granados" <joel.granados@kernel.org>,
"Anna Schumaker" <anna.schumaker@oracle.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
zhangguopeng <zhangguopeng@kylinos.cn>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Neeraj Upadhyay (AMD)" <neeraj.iitr10@gmail.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-rt-devel@lists.linux.dev,
"Breno Leitao" <leitao@debian.org>,
"Valentin Schneider" <vschneid@redhat.com>
Subject: [PATCH rcu 06/10] context_tracking: Make RCU watch ct_kernel_exit_state() warning
Date: Tue, 4 Mar 2025 19:05:01 -0800 [thread overview]
Message-ID: <20250305030505.94059-7-boqun.feng@gmail.com> (raw)
In-Reply-To: <20250305030505.94059-1-boqun.feng@gmail.com>
From: "Paul E. McKenney" <paulmck@kernel.org>
The WARN_ON_ONCE() in ct_kernel_exit_state() follows the call to
ct_state_inc(), which means that RCU is not watching this WARN_ON_ONCE().
This can (and does) result in extraneous lockdep warnings when this
WARN_ON_ONCE() triggers. These extraneous warnings are the opposite
of helpful.
Therefore, invert the WARN_ON_ONCE() condition and move it before the
call to ct_state_inc(). This does mean that the ct_state_inc() return
value can no longer be used in the WARN_ON_ONCE() condition, so discard
this return value and instead use a call to rcu_is_watching_curr_cpu().
This call is executed only in CONFIG_RCU_EQS_DEBUG=y kernels, so there
is no added overhead in production use.
[Boqun: Add the subsystem tag in the title]
Reported-by: Breno Leitao <leitao@debian.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Reviewed-by: Valentin Schneider <vschneid@redhat.com>
Reviewed-by: Frederic Weisbecker <frederic@kernel.org>
Link: https://lore.kernel.org/r/bd911cd9-1fe9-447c-85e0-ea811a1dc896@paulmck-laptop
Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
---
kernel/context_tracking.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/kernel/context_tracking.c b/kernel/context_tracking.c
index 938c48952d26..fb5be6e9b423 100644
--- a/kernel/context_tracking.c
+++ b/kernel/context_tracking.c
@@ -80,17 +80,16 @@ static __always_inline void rcu_task_trace_heavyweight_exit(void)
*/
static noinstr void ct_kernel_exit_state(int offset)
{
- int seq;
-
/*
* CPUs seeing atomic_add_return() must see prior RCU read-side
* critical sections, and we also must force ordering with the
* next idle sojourn.
*/
rcu_task_trace_heavyweight_enter(); // Before CT state update!
- seq = ct_state_inc(offset);
- // RCU is no longer watching. Better be in extended quiescent state!
- WARN_ON_ONCE(IS_ENABLED(CONFIG_RCU_EQS_DEBUG) && (seq & CT_RCU_WATCHING));
+ // RCU is still watching. Better not be in extended quiescent state!
+ WARN_ON_ONCE(IS_ENABLED(CONFIG_RCU_EQS_DEBUG) && !rcu_is_watching_curr_cpu());
+ (void)ct_state_inc(offset);
+ // RCU is no longer watching.
}
/*
--
2.48.1
next prev parent reply other threads:[~2025-03-05 3:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 3:04 [PATCH rcu 00/10] Miscellaneous RCU changes for v6.15 Boqun Feng
2025-03-05 3:04 ` [PATCH rcu 01/10] rcu: Split rcu_report_exp_cpu_mult() mask parameter and use for tracing Boqun Feng
2025-03-05 3:04 ` [PATCH rcu 02/10] rcu: Remove READ_ONCE() for rdp->gpwrap access in __note_gp_changes() Boqun Feng
2025-03-05 3:04 ` [PATCH rcu 03/10] rcu: Fix get_state_synchronize_rcu_full() GP-start detection Boqun Feng
2025-03-05 3:04 ` [PATCH rcu 04/10] rcu-tasks: Move RCU Tasks self-tests to core_initcall() Boqun Feng
2025-03-05 3:05 ` [PATCH rcu 05/10] rcu/nocb: Print segment lengths in show_rcu_nocb_gp_state() Boqun Feng
2025-03-05 3:05 ` Boqun Feng [this message]
2025-03-05 3:05 ` [PATCH rcu 07/10] Flush console log from kernel_power_off() Boqun Feng
2025-03-05 3:05 ` [PATCH rcu 08/10] rcutorture: Allow a negative value for nfakewriters Boqun Feng
2025-03-05 3:05 ` [PATCH rcu 09/10] rcu: Update TREE05.boot to test normal synchronize_rcu() Boqun Feng
2025-03-05 3:05 ` [PATCH rcu 10/10] rcu: Use _full() API to debug synchronize_rcu() Boqun Feng
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=20250305030505.94059-7-boqun.feng@gmail.com \
--to=boqun.feng@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anna.schumaker@oracle.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=dave@stgolabs.net \
--cc=frederic@kernel.org \
--cc=guoweikang.kernel@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel.granados@kernel.org \
--cc=joel@joelfernandes.org \
--cc=john.ogness@linutronix.de \
--cc=josh@joshtriplett.org \
--cc=kpsingh@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@weissschuh.net \
--cc=martin.petersen@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=neeraj.iitr10@gmail.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rrangel@chromium.org \
--cc=senozhatsky@chromium.org \
--cc=shijie@os.amperecomputing.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=vschneid@redhat.com \
--cc=ytcoode@gmail.com \
--cc=zhangguopeng@kylinos.cn \
/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