From: Joel Fernandes <joelagnelf@nvidia.com>
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 <joel@joelfernandes.org>,
Boqun Feng <boqun.feng@gmail.com>,
Uladzislau Rezki <urezki@gmail.com>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
qiang.zhang1211@gmail.com
Subject: [GIT PULL] RCU fixes for v6.16 -rc3
Date: Fri, 20 Jun 2025 15:52:34 -0400 [thread overview]
Message-ID: <20250620195234.GA3336282@joelnvbox> (raw)
Hi Linus,
The following changes since commit 11313e2f78128c948e9b4eb58b3dacfc30964700:
Merge tag 'gpio-fixes-for-v6.16-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux (2025-06-20 10:07:56 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git tags/rcu/fixes-for-6.16-rc3
for you to fetch changes up to 33b6a1f155d627f5bd80c7485c598ce45428f74f:
rcu: Return early if callback is not specified (2025-06-20 15:31:48 -0400)
----------------------------------------------------------------
We recently got a report of a crash [1] with misuse of call_rcu().
Instead of crashing the kernel, a warning and graceful return is better.
[1] https://lore.kernel.org/all/aEnVuzK7VhGSizWj@pc636/
Uladzislau Rezki (Sony) (1):
rcu: Return early if callback is not specified
kernel/rcu/tree.c | 4 ++++
1 file changed, 4 insertions(+)
----------------------------------------------------------------
Uladzislau Rezki (Sony) (1):
rcu: Return early if callback is not specified
kernel/rcu/tree.c | 4 ++++
1 file changed, 4 insertions(+)
next reply other threads:[~2025-06-20 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 19:52 Joel Fernandes [this message]
2025-06-21 15:47 ` [GIT PULL] RCU fixes for v6.16 -rc3 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=20250620195234.GA3336282@joelnvbox \
--to=joelagnelf@nvidia.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.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 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.