public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: Boqun Feng <boqun.feng@gmail.com>,
	Joel Fernandes <joelagnelf@nvidia.com>
Cc: Boqun Feng <boqun.feng@gmail.com>,
	Joel Fernandes <joelagnelf@nvidia.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	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>,
	Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: Re: [PATCH v4 3/3] rcu: Use _full() API to debug synchronize_rcu()
Date: Tue, 4 Mar 2025 11:56:18 +0100	[thread overview]
Message-ID: <Z8bcUsZ9IpRi1QoP@pc636> (raw)
In-Reply-To: <Z8bbary51FZ2TsUA@pc636>

On Tue, Mar 04, 2025 at 11:52:26AM +0100, Uladzislau Rezki wrote:
> > > Did I get that right?
> > > 
> > 
> > Other than I'm unable to follow what do you mean "WH has not been
> > injected, so nothing to wait on", maybe because I am missing some
> > terminology from you ;-) I think it's a good analysis, thank you!
> > 
> > > I think this is a real bug AFAICS, hoping all the memory barriers are in
> > > place to make sure the code reordering also correctly orders the accesses.
> > > I'll double check that.
> > > 
> > > I also feel its 'theoretical', because as long as rcu_gp_init() and
> > > rcu_gp_cleanup() are properly ordered WRT pre-existing readers, then
> > > synchronize_rcu_normal() still waits for pre-existing readers even though its
> > > a bit confused about the value of the cookies.
> > > 
> > > For the fix,
> > > Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>
> > > 
> > > (If possible, include a Link: to my (this) post so that the sequence of
> > > events is further clarified.)
> > > 
> > 
> > Will add the tag (with the email you really want ;-)) and a link to this
> > email to the patch. Thanks!
> > 
> 
> CPU_1:                                | CPU_2:
>   # Increase a seq-number             |
>   rcu_seq_start(&rcu_state.gp_seq);   |
>                                       | add_client() {
> 				      |   # Record a gp-sec state 
> 				      |   get_state_synchronize_rcu_full(&rs.oldstate);
>                                       | }
>                                       |
>                                       | rcu_sr_normal_gp_init() {
> 				      |   add a dummy-wait-head;
> 				      | }
> 
> 
> A client has been added with already updated gp-sec number, i.e.
> "oldstate" would refer to this GP, not to previous. A poll_state_synchronize_rcu_full()
> will complain because this GP is not passed, it will on a next iteration.
> 
> This is how i see this.
> 
Updated the plain-text, removed tabs:

CPU_1:                                 | CPU_2:
   # Increase a seq-number             |
   rcu_seq_start(&rcu_state.gp_seq);   |
                                       | add_client() {
                                       |   # Record a gp-sec state 
                                       |   get_state_synchronize_rcu_full(&rs.oldstate);
                                       | }
                                       |
                                       | rcu_sr_normal_gp_init() {
                                       |   add a dummy-wait-head;
                                       | }

--
Uladzislau Rezki

  reply	other threads:[~2025-03-04 10:56 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 ` [PATCH v4 3/3] rcu: Use _full() API to debug synchronize_rcu() Uladzislau Rezki (Sony)
2025-02-27 17:12   ` 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 [this message]
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=Z8bcUsZ9IpRi1QoP@pc636 \
    --to=urezki@gmail.com \
    --cc=Neeraj.Upadhyay@amd.com \
    --cc=boqun.feng@gmail.com \
    --cc=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=joelagnelf@nvidia.com \
    --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