From: Uladzislau Rezki <urezki@gmail.com>
To: Boqun Feng <boqun@kernel.org>
Cc: Uladzislau Rezki <urezki@gmail.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
paulmck@kernel.org, Boqun Feng <boqun.feng@gmail.com>,
Joel Fernandes <joelagnelf@nvidia.com>, RCU <rcu@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>,
Frederic Weisbecker <frederic@kernel.org>,
Samir <samir@linux.ibm.com>,
Shrikanth Hegde <sshegde@linux.ibm.com>,
Tejun Heo <tj@kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH -next v1 05/12] srcu: Don't queue workqueue handlers to never-online CPUs
Date: Tue, 19 May 2026 15:19:00 +0200 [thread overview]
Message-ID: <agxjRHuAnzHFDqD9@milan> (raw)
In-Reply-To: <agtowPsNCB2LioTN@tardis.local>
On Mon, May 18, 2026 at 12:30:08PM -0700, Boqun Feng wrote:
> On Mon, May 18, 2026 at 07:05:36PM +0200, Uladzislau Rezki wrote:
> > On Mon, May 18, 2026 at 09:13:46AM -0700, Boqun Feng wrote:
> > > On Sun, May 17, 2026 at 09:11:10PM +0200, Thorsten Leemhuis wrote:
> > > > On 5/17/26 20:03, Paul E. McKenney wrote:
> > > > > On Sun, May 17, 2026 at 02:47:55PM +0200, Uladzislau Rezki wrote:
> > > > >> On Wed, May 13, 2026 at 12:38:01PM +0200, Thorsten Leemhuis wrote:
> > > > >>> On 5/11/26 19:54, Uladzislau Rezki (Sony) wrote:
> > > > >>>> From: "Paul E. McKenney" <paulmck@kernel.org>
> > > > >>>>
> > > > >>>> While an srcu_struct structure is in the midst of switching from CPU-0
> > > > >>>> to all-CPUs state, it can attempt to invoke callbacks for CPUs that
> > > > >>>> have never been online. Worse yet, it can attempt in invoke callbacks
> > > > >>>> for CPUs that never will be online, even including imaginary CPUs not in
> > > > >>>> cpu_possible_mask. This can cause hangs on s390,
> > > > >>>
> > > > >>> Uladzislau, Paul, according to the fixes tag below this change fixes a
> > > > >>> change that went into 7.0-rc6 -- and apparently causes a "hang" on some
> > > > >>> architectures. So shouldn't this be heading to mainline instead of
> > > > >>> -next? Ideally with a stable tag to ensure backporting to 7.0.y, but
> > > > >>> that is a separate decision?
> > > > >>>
> > >
> > > FWIW, I'm happy to create an urgent PR to Linus with this fix. Since it
> > > fixes a commit in the previous urgent fix PR from me. Ulad, let me know
> > > if you want me to do it.
> > >
> > I do not mind :) So i can drop this patch!
> >
>
> Alright, I created the fix branch at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git/log/?h=fixes.v7.1
>
> And I'm going to throw some tests on it. Will send the pull request
> tomorrow.
>
Cool, then i drop this patch!
--
Uladzislau Rezki
next prev parent reply other threads:[~2026-05-19 13:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 17:54 [PATCH -next v1 00/12] Candidate patches for the v7.2 merge window Uladzislau Rezki (Sony)
2026-05-11 17:54 ` [PATCH -next v1 01/12] rcutorture: Fully test lazy RCU Uladzislau Rezki (Sony)
2026-05-14 13:33 ` Z qiang
2026-05-17 12:40 ` Uladzislau Rezki
2026-05-17 18:30 ` Paul E. McKenney
2026-05-18 15:36 ` Uladzislau Rezki
2026-05-19 0:38 ` Paul E. McKenney
2026-05-19 16:04 ` Uladzislau Rezki
2026-05-11 17:54 ` [PATCH -next v1 02/12] torture: Add torture_sched_set_normal() for user-specified nice values Uladzislau Rezki (Sony)
2026-05-11 17:54 ` [PATCH -next v1 03/12] torture: Improve kvm-series.sh header comment Uladzislau Rezki (Sony)
2026-05-11 17:54 ` [PATCH -next v1 04/12] torture: Allow "norm" abbreviation for "normal" Uladzislau Rezki (Sony)
2026-05-11 17:54 ` [PATCH -next v1 05/12] srcu: Don't queue workqueue handlers to never-online CPUs Uladzislau Rezki (Sony)
2026-05-13 10:38 ` Thorsten Leemhuis
2026-05-17 12:47 ` Uladzislau Rezki
2026-05-17 18:03 ` Paul E. McKenney
2026-05-17 19:11 ` Thorsten Leemhuis
2026-05-18 16:13 ` Boqun Feng
2026-05-18 17:05 ` Uladzislau Rezki
2026-05-18 19:30 ` Boqun Feng
2026-05-19 13:19 ` Uladzislau Rezki [this message]
2026-05-19 4:52 ` Jiri Slaby
2026-05-11 17:54 ` [PATCH -next v1 06/12] srcu: Fix kerneldoc header comment typo in srcu_down_read_fast() Uladzislau Rezki (Sony)
2026-05-11 17:54 ` [PATCH -next v1 07/12] checkpatch: Undeprecate rcu_read_lock_trace() and rcu_read_unlock_trace() Uladzislau Rezki (Sony)
2026-05-11 17:54 ` [PATCH -next v1 08/12] rcu: Simplify rcu_do_batch() by applying clamp() Uladzislau Rezki (Sony)
2026-05-11 17:54 ` [PATCH -next v1 09/12] rcu: Simplify param_set_next_fqs_jiffies() by applying clamp_val() Uladzislau Rezki (Sony)
2026-05-11 17:54 ` [PATCH -next v1 10/12] rcu: Document rcu_access_pointer() feeding into cmpxchg() Uladzislau Rezki (Sony)
2026-05-11 17:54 ` [PATCH -next v1 11/12] rcu: Latch normal synchronize_rcu() path on flood Uladzislau Rezki (Sony)
2026-05-11 17:54 ` [PATCH -next v1 12/12] rcu-tasks: Fix possible boot-time tests failed for the call_rcu_tasks() Uladzislau Rezki (Sony)
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=agxjRHuAnzHFDqD9@milan \
--to=urezki@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=boqun@kernel.org \
--cc=frederic@kernel.org \
--cc=gor@linux.ibm.com \
--cc=jirislaby@kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=samir@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=tj@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