From: Boqun Feng <boqun@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, rostedt@goodmis.org
Subject: Re: [PATCH 0/4] rcu: Fix lazy-preemption regression in torture-test suites
Date: Thu, 5 Mar 2026 13:29:04 -0800 [thread overview]
Message-ID: <aan1oNttjGU-uNu_@tardis.local> (raw)
In-Reply-To: <2011d452-3c72-432a-af77-810238e80e6a@paulmck-laptop>
On Tue, Mar 03, 2026 at 03:58:56PM -0800, Paul E. McKenney wrote:
> Hello!
>
> As of v7.0-rc1, architectures that support preemption, including x86 and
> arm64, no longer support CONFIG_PREEMPT_NONE or CONFIG_PREEMPT_VOLUNTARY.
> Attempting to build kernels with these two Kconfig options results in
> .config errors, which causes torture-test programs such as rcutorture
> to throw false-positive errors. This series fixes this v7.0-rc1
> regression by converting these scanarios from CONFIG_PREEMPT_NONE=y or
> CONFIG_PREEMPT_VOLUNTARY=y to CONFIG_PREEMPT_LAZY=y.
>
> Those maintaining architectures not supporting preemption might wish to
> run rcutorture with CONFIG_PREEMPT_NONE=y and CONFIG_PREEMPT_VOLUNTARY=y
> because I no longer have access to any systems supporting these Kconfig
> choices.
>
> With all that said, the patches are as follows:
>
> 1. rcutorture: Update due to x86 not supporting none/voluntary
> preemption.
>
> 2. rcuscale: Update due to x86 not supporting none/voluntary
> preemption.
>
> 3. refscale: Update due to x86 not supporting none/voluntary
> preemption.
>
> 4. scftorture: Update due to x86 not supporting none/voluntary
> preemption.
>
I queued this series at:
https://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git/ fixes.v7.0
based on v7.0-rc2, and I'm running some test from my end. If everything
goes well, I will send a fix PR before -rc3. Thank you both!
Regards,
Boqun
> Thanx, Paul
>
> ------------------------------------------------------------------------
>
> rcu/SRCU-N | 3 ++-
> rcu/SRCU-T | 3 ++-
> rcu/SRCU-U | 3 ++-
> rcu/TASKS02 | 3 ++-
> rcu/TINY01 | 3 ++-
> rcu/TINY02 | 3 ++-
> rcu/TRACE01 | 3 ++-
> rcu/TREE04 | 3 ++-
> rcu/TREE05 | 3 ++-
> rcu/TREE06 | 3 ++-
> rcu/TRIVIAL | 3 ++-
> rcuscale/TINY | 3 ++-
> rcuscale/TRACE01 | 3 ++-
> refscale/NOPREEMPT | 3 ++-
> refscale/TINY | 3 ++-
> scf/NOPREEMPT | 3 ++-
> 16 files changed, 32 insertions(+), 16 deletions(-)
>
prev parent reply other threads:[~2026-03-05 21:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 23:58 [PATCH 0/4] rcu: Fix lazy-preemption regression in torture-test suites Paul E. McKenney
2026-03-03 23:59 ` [PATCH 1/4] rcutorture: Update due to x86 not supporting none/voluntary preemption Paul E. McKenney
2026-03-04 17:26 ` [PATCH v2 " Paul E. McKenney
2026-03-05 0:01 ` [PATCH v3 " Paul E. McKenney
2026-03-05 17:53 ` Joel Fernandes
2026-03-05 19:08 ` Paul E. McKenney
2026-03-05 18:22 ` Boqun Feng
2026-03-05 19:06 ` Paul E. McKenney
2026-03-05 19:59 ` Boqun Feng
2026-03-05 20:11 ` Paul E. McKenney
2026-03-05 21:08 ` Boqun Feng
2026-03-05 23:24 ` Paul E. McKenney
2026-03-03 23:59 ` [PATCH 2/4] rcuscale: " Paul E. McKenney
2026-03-03 23:59 ` [PATCH 3/4] refscale: " Paul E. McKenney
2026-03-03 23:59 ` [PATCH 4/4] scftorture: " Paul E. McKenney
2026-03-05 21:29 ` Boqun Feng [this message]
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=aan1oNttjGU-uNu_@tardis.local \
--to=boqun@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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 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.