From: Boqun Feng <boqun.feng@gmail.com>
To: Joel Fernandes <joelagnelf@nvidia.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>, 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: Mon, 3 Mar 2025 09:07:30 -0800 [thread overview]
Message-ID: <Z8Xh0pP4xaFm0nEV@tardis> (raw)
In-Reply-To: <20250303170040.GA31126@joelnvbox>
On Mon, Mar 03, 2025 at 12:00:40PM -0500, Joel Fernandes wrote:
[...]
>
> I see the original patch "rcu: Fix get_state_synchronize_rcu_full() GP-start
> detection" is not yet on -next. Once we are convinced about the fix, do we
> want to squash the fix into this patch and have Boqun take it?
>
Which "-next" are you talking about? The original patch and the fix is
already in next-20250303 of linux-next:
https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?h=next-20250303&qt=range&q=153fc45000e0058435ec0609258fb16e7ea257d2
Regards,
Boqun
> Yet another idea is to apply it for 6.15-rc cycle if more time is needed.
>
> Alternatively, we could squash it and I queue it for 6.16 instead of 6.15.
>
> And I'm guessing Vlad's series is also for 6.16.
>
> thanks,
>
> - Joel
>
next prev parent reply other threads:[~2025-03-03 17:07 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 [this message]
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=Z8Xh0pP4xaFm0nEV@tardis \
--to=boqun.feng@gmail.com \
--cc=Neeraj.Upadhyay@amd.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=urezki@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.