From: Boqun Feng <boqun@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <joelagnelf@nvidia.com>,
Uladzislau Rezki <urezki@gmail.com>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>
Subject: [GIT PULL] RCU fixes for v7.0
Date: Sat, 7 Mar 2026 10:05:17 -0800 [thread overview]
Message-ID: <aaxo3f8V-IM8WGpf@tardis.local> (raw)
Hi Linus,
Please pull these RCU fixes into v7.0. The issue is that some
pre-defined scenarios in RCU torture tests have not adjusted the recent
PREEMPT_LAZY kconfig changes. I could have found it if I ran rcutorture
against linux-next, will do that next time. Thankfully Paul found and
fixed it quickly ;-)
The following changes since commit 11439c4635edd669ae435eec308f4ab8a0804808:
Linux 7.0-rc2 (2026-03-01 15:39:31 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git tags/rcu-fixes.v7.0-20260307a
for you to fetch changes up to 78c2ce0fd6ddb6c87aaa56b0d49c70e17df21e6d:
scftorture: Update due to x86 not supporting none/voluntary preemption (2026-03-05 13:11:10 -0800)
----------------------------------------------------------------
RCU fixes for v7.0
Fix a regression in RCU torture test pre-defined scenarios caused by
commit 7dadeaa6e851 ("sched: Further restrict the preemption modes")
which limits PREEMPT_NONE to architectures that do not support
preemption at all and PREEMPT_VOLUNTARY to those architectures that do
not yet have PREEMPT_LAZY support. Since major architectures (e.g. x86
and arm64) no longer support CONFIG_PREEMPT_NONE and
CONFIG_PREEMPT_VOLUNTARY, using them in rcutorture, rcuscale, refscale,
and scftorture pre-defined scenarios causes config checking errors.
Hence switch these kconfigs to PREEMPT_LAZY.
-----BEGIN PGP SIGNATURE-----
iQFFBAABCAAvFiEEj5IosQTPz8XU1wRHSXnow7UH+rgFAmmsZu0RHGJvcXVuQGtl
cm5lbC5vcmcACgkQSXnow7UH+rgNWwgAn1bIWDIWQR9CkRQ0grhdO+pPfLusbVg/
Y7H3SsdEX03meSunA/IVGejP6Qbanuab9nyHdv3WxxowpCGYBaLFPvklSfcBWYeZ
4lxi6Fj+2rrzvOnQ54Pk5i4v5VayxEo12XBIgx6HDV7+5LgWk0gU0LpWPUhEWYYR
z/zJ/XbcLr8e9tZVwAWZj/ShLUH301razC2SaR/OlS93zqRG9Sd251Knjqq/lEwI
T6RZfhT2Wz3bgqU3QcjxDWw5dhB0/Y9wKoJjx4bB9m8lnSt+o96gH40TO+lnllnS
T4OHjqK1J1fUXNLzQufyfKKAiwi/LBBc9H4pe4tiLFxg0fg5s21flQ==
=NBys
-----END PGP SIGNATURE-----
Regards,
Boqun
----------------------------------------------------------------
Paul E. McKenney (4):
rcutorture: Update due to x86 not supporting none/voluntary preemption
rcuscale: Update due to x86 not supporting none/voluntary preemption
refscale: Update due to x86 not supporting none/voluntary preemption
scftorture: Update due to x86 not supporting none/voluntary preemption
tools/testing/selftests/rcutorture/configs/rcu/SRCU-N | 4 +++-
tools/testing/selftests/rcutorture/configs/rcu/SRCU-T | 3 ++-
tools/testing/selftests/rcutorture/configs/rcu/SRCU-U | 4 ++--
tools/testing/selftests/rcutorture/configs/rcu/TASKS02 | 3 ++-
tools/testing/selftests/rcutorture/configs/rcu/TINY01 | 4 ++--
tools/testing/selftests/rcutorture/configs/rcu/TINY02 | 3 ++-
tools/testing/selftests/rcutorture/configs/rcu/TRACE01 | 3 ++-
tools/testing/selftests/rcutorture/configs/rcu/TREE04 | 4 +++-
tools/testing/selftests/rcutorture/configs/rcu/TREE05 | 4 +++-
tools/testing/selftests/rcutorture/configs/rcu/TREE06 | 5 ++++-
tools/testing/selftests/rcutorture/configs/rcu/TREE10 | 1 +
tools/testing/selftests/rcutorture/configs/rcu/TRIVIAL | 4 +++-
tools/testing/selftests/rcutorture/configs/rcuscale/TINY | 3 ++-
tools/testing/selftests/rcutorture/configs/rcuscale/TRACE01 | 3 ++-
tools/testing/selftests/rcutorture/configs/refscale/NOPREEMPT | 3 ++-
tools/testing/selftests/rcutorture/configs/refscale/TINY | 3 ++-
tools/testing/selftests/rcutorture/configs/scf/NOPREEMPT | 3 ++-
17 files changed, 39 insertions(+), 18 deletions(-)
next reply other threads:[~2026-03-07 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 18:05 Boqun Feng [this message]
2026-03-07 20:00 ` [GIT PULL] RCU fixes for v7.0 pr-tracker-bot
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=aaxo3f8V-IM8WGpf@tardis.local \
--to=boqun@kernel.org \
--cc=frederic@kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=urezki@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