From: Joel Fernandes <jfern@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>,
Boqun Feng <boqun@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Nathan Chancellor <nathan@kernel.org>, Song Liu <song@kernel.org>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
llvm@lists.linux.dev
Subject: [GIT PULL] RCU fixes for v7.4
Date: Sun, 15 Nov 2026 19:15:56 -0500 [thread overview]
Message-ID: <20261116001556.763913-1-jfern@kernel.org> (raw)
Hi Linus,
Please pull these RCU fixes into v7.4.
The following changes since commit aebb7274476403040d582c61478df8f4a7bf9cd3:
Linux 7.4-rc3 (2026-11-15 14:30:11 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git tags/rcu-fixes.v7.4-20261115a
for you to fetch changes up to c3f98ff6309a29979e1867bc3c9d4172755ca122:
rcu/nocb: Avoid unsequenced accesses to jiffies in show_rcu_nocb_state() (2026-11-15 18:52:04 -0500)
----------------------------------------------------------------
RCU fixes for v7.4
Fix a build break with recent clang, which warns about unsequenced
accesses to the volatile jiffies variable in show_rcu_nocb_state() and
fails the build with CONFIG_WERROR=y / W=e. Read jiffies once into a
local variable instead.
Also replace the rcupdate.rcu_task_collapse_debug module parameter, added
in the v7.4 merge window, with pr_debug() for the RCU Tasks callback
contend/collapse messages. The messages stay off by default and can be
enabled with dynamic debug, and no official kernel carries the extra
parameter.
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEcoCIrlGe4gjE06JJqA4nf2o45hAFAmr6RvAACgkQqA4nf2o4
5hCnfg/8DqHU2c4j5ZLgYK7oD99BNg4VTErwkBwwx8eCRb87agrdljsQo8keZBwB
BSbN+gaasl3NvqKUh7lAopAvoZtfk3ymtw4oafDCHa5jJFZV1E2bGUbDBKBwuzlj
6BBHEPFitd5q6z6nlyhSx7289NYoRhr9InMNv/L2kYKnn4bq79Ojf1Z5nQZRHPRz
TUGIwDoVf0G+oh0z2TtrMSNAC4OBPP7Hsq2/m3xaeS2pWS8YziFM7rXcnJaWve4t
D4VjZGWOTQCWOCeYBbyckXSa2zLBSlwCfarbkPfpo1FhdcwBmXdeNvt9MnZ2sRP0
Ff/x+rd5LkzQ3niHYufuxflGv5XLoiaJgiU9rztlD9U2O9sheVaRcf7BaDs77C+f
NmteR2H67svHfK93bOgTNvFVBX90Y4Qa4WPft6g9QbuGkIGD6hJRBbveTeCNsbPM
vmvU/cPYwjcpGZiyPcglpAoIYK8e9F7hspXrpvJTjnoF0p1b2TefpHZS+ozZIcj8
6uD28K2dp+CLAzuLkC5FzgITvWPdIEYiEq9WD0A/kOPO5fZ0+BmOiekb4iBnnHdK
H6HujCvGYhwLGqlJ1aoc7VxoQp+zz9ZOwJzQ4pV9xO/WiHZroEiQvinsgs1+NYOb
jATSr9YPap8CNRqjwMNXK1ppKKkfPdix+JYcx4/WGFzZhCiDM54=
=tbXB
-----END PGP SIGNATURE-----
thanks,
Joel Fernandes
----------------------------------------------------------------
Nathan Chancellor (1):
rcu/nocb: Avoid unsequenced accesses to jiffies in show_rcu_nocb_state()
Song Liu (1):
rcu-tasks: Use pr_debug() for callback contend/collapse messages
Documentation/admin-guide/kernel-parameters.txt | 7 -------
kernel/rcu/tasks.h | 15 +++------------
kernel/rcu/tree_nocb.h | 6 ++++--
3 files changed, 7 insertions(+), 21 deletions(-)
reply other threads:[~2026-11-16 0:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261116001556.763913-1-jfern@kernel.org \
--to=jfern@kernel.org \
--cc=boqun@kernel.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=song@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
all inboxes | Powered by JetHome®