public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
To: "Paul E . McKenney" <paulmck@kernel.org>,
	Boqun Feng <boqun.feng@gmail.com>
Cc: RCU <rcu@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	Cheung Wall <zzqq0103.hey@gmail.com>,
	Neeraj upadhyay <Neeraj.Upadhyay@amd.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	Uladzislau Rezki <urezki@gmail.com>,
	Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: [PATCH v4 3/3] rcu: Use _full() API to debug synchronize_rcu()
Date: Thu, 27 Feb 2025 14:16:13 +0100	[thread overview]
Message-ID: <20250227131613.52683-3-urezki@gmail.com> (raw)
In-Reply-To: <20250227131613.52683-1-urezki@gmail.com>

Switch for using of get_state_synchronize_rcu_full() and
poll_state_synchronize_rcu_full() pair to debug a normal
synchronize_rcu() call.

Just using "not" full APIs to identify if a grace period is
passed or not might lead to a false-positive kernel splat.

It can happen, because get_state_synchronize_rcu() compresses
both normal and expedited states into one single unsigned long
value, so a poll_state_synchronize_rcu() can miss GP-completion
when synchronize_rcu()/synchronize_rcu_expedited() concurrently
run.

To address this, switch to poll_state_synchronize_rcu_full() and
get_state_synchronize_rcu_full() APIs, which use separate variables
for expedited and normal states.

Link: https://lore.kernel.org/lkml/Z5ikQeVmVdsWQrdD@pc636/T/
Fixes: 988f569ae041 ("rcu: Reduce synchronize_rcu() latency")
Reported-by: cheung wall <zzqq0103.hey@gmail.com>
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
---
 include/linux/rcupdate_wait.h | 3 +++
 kernel/rcu/tree.c             | 8 +++-----
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/include/linux/rcupdate_wait.h b/include/linux/rcupdate_wait.h
index f9bed3d3f78d..4c92d4291cce 100644
--- a/include/linux/rcupdate_wait.h
+++ b/include/linux/rcupdate_wait.h
@@ -16,6 +16,9 @@
 struct rcu_synchronize {
 	struct rcu_head head;
 	struct completion completion;
+
+	/* This is for debugging. */
+	struct rcu_gp_oldstate oldstate;
 };
 void wakeme_after_rcu(struct rcu_head *head);
 
diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
index 8625f616c65a..48384fa2eaeb 100644
--- a/kernel/rcu/tree.c
+++ b/kernel/rcu/tree.c
@@ -1632,12 +1632,10 @@ static void rcu_sr_normal_complete(struct llist_node *node)
 {
 	struct rcu_synchronize *rs = container_of(
 		(struct rcu_head *) node, struct rcu_synchronize, head);
-	unsigned long oldstate = (unsigned long) rs->head.func;
 
 	WARN_ONCE(IS_ENABLED(CONFIG_PROVE_RCU) &&
-		!poll_state_synchronize_rcu(oldstate),
-		"A full grace period is not passed yet: %lu",
-		rcu_seq_diff(get_state_synchronize_rcu(), oldstate));
+		!poll_state_synchronize_rcu_full(&rs->oldstate),
+		"A full grace period is not passed yet!\n");
 
 	/* Finally. */
 	complete(&rs->completion);
@@ -3247,7 +3245,7 @@ static void synchronize_rcu_normal(void)
 	 * snapshot before adding a request.
 	 */
 	if (IS_ENABLED(CONFIG_PROVE_RCU))
-		rs.head.func = (void *) get_state_synchronize_rcu();
+		get_state_synchronize_rcu_full(&rs.oldstate);
 
 	rcu_sr_normal_add_req(&rs);
 
-- 
2.39.5


  parent reply	other threads:[~2025-02-27 13:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 13:16 [PATCH v4 1/3] rcutorture: Allow a negative value for nfakewriters Uladzislau Rezki (Sony)
2025-02-27 13:16 ` [PATCH v4 2/3] rcu: Update TREE05.boot to test normal synchronize_rcu() Uladzislau Rezki (Sony)
2025-02-27 13:16 ` Uladzislau Rezki (Sony) [this message]
2025-02-27 17:12   ` [PATCH v4 3/3] rcu: Use _full() API to debug synchronize_rcu() Boqun Feng
2025-02-27 17:26     ` Paul E. McKenney
2025-02-27 17:30       ` Boqun Feng
2025-02-27 17:44       ` Uladzislau Rezki
2025-02-28 15:41         ` Paul E. McKenney
2025-02-28 16:36           ` Uladzislau Rezki
2025-02-28 17:08             ` Uladzislau Rezki
2025-02-28 18:25               ` Paul E. McKenney
2025-02-28 18:30                 ` Uladzislau Rezki
2025-02-28 18:21             ` Paul E. McKenney
2025-02-28 18:24               ` Uladzislau Rezki
2025-02-28 18:38                 ` Paul E. McKenney
2025-02-28 19:12                   ` Uladzislau Rezki
2025-02-28 19:59                     ` Paul E. McKenney
2025-03-01  1:08                       ` Paul E. McKenney
2025-03-02 10:19                         ` Uladzislau Rezki
2025-03-02 17:39                           ` Paul E. McKenney
2025-03-02 18:46                             ` Boqun Feng
2025-03-02 20:36                               ` Paul E. McKenney
2025-03-03 16:03                                 ` Uladzislau Rezki
2025-03-03  0:15                         ` Joel Fernandes
2025-03-03  0:17                           ` Joel Fernandes
2025-03-03 17:00                             ` Joel Fernandes
2025-03-03 17:07                               ` Boqun Feng
2025-03-03 17:30                                 ` Joel Fernandes
2025-03-03 17:59                                   ` Joel Fernandes
2025-03-03 18:55                                   ` Paul E. McKenney
2025-03-03 20:02                                     ` Joel Fernandes
2025-03-04  3:23                           ` Boqun Feng
2025-03-04 10:52                             ` Uladzislau Rezki
2025-03-04 10:56                               ` Uladzislau Rezki
2025-03-05  2:54                                 ` Boqun Feng
2025-03-05 15:37                                   ` Joel Fernandes
2025-03-05 15:24                             ` Joel Fernandes
2025-02-27 17:43     ` Uladzislau Rezki
2025-03-10  1:55   ` Joel Fernandes
2025-03-11 12:38     ` Uladzislau Rezki

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=20250227131613.52683-3-urezki@gmail.com \
    --to=urezki@gmail.com \
    --cc=Neeraj.Upadhyay@amd.com \
    --cc=boqun.feng@gmail.com \
    --cc=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksiy.avramchenko@sony.com \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=zzqq0103.hey@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