From: Joel Fernandes <joelagnelf@nvidia.com>
To: paulmck@kernel.org, Gustavo Luiz Duarte <gustavold@gmail.com>
Cc: Breno Leitao <leitao@debian.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: Add BOOTPARAM_RCU_STALL_PANIC Kconfig option
Date: Tue, 17 Mar 2026 17:39:53 -0400 [thread overview]
Message-ID: <17ec3354-934a-48c3-8ed1-a68bf838e524@nvidia.com> (raw)
In-Reply-To: <3dbfa497-091f-4538-8926-13f33fed3603@paulmck-laptop>
On 3/13/2026 1:07 PM, Paul E. McKenney wrote:
> On Fri, Mar 13, 2026 at 09:56:49AM -0700, Gustavo Luiz Duarte wrote:
>> Add a Kconfig option to set the default value of the
>> kernel.panic_on_rcu_stall sysctl, allowing the kernel to be built
>> with panic-on-RCU-stall enabled by default.
>>
>> This is useful for high-availability systems that require automatic
>> recovery (via panic_timeout) when a CPU stall is detected, without
>> needing userspace to configure the sysctl at boot.
>>
>> This follows the pattern established by BOOTPARAM_SOFTLOCKUP_PANIC
>> and BOOTPARAM_HUNG_TASK_PANIC. The runtime sysctl can still override
>> the Kconfig default.
>>
>> Signed-off-by: Gustavo Luiz Duarte <gustavold@gmail.com>
>
> Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
Applied for 7.1, thanks!
--
Joel Fernandes
next prev parent reply other threads:[~2026-03-17 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 16:56 Gustavo Luiz Duarte
2026-03-13 17:07 ` Paul E. McKenney
2026-03-17 21:39 ` Joel Fernandes [this message]
2026-03-13 17:43 ` Breno Leitao
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=17ec3354-934a-48c3-8ed1-a68bf838e524@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=boqun@kernel.org \
--cc=frederic@kernel.org \
--cc=gustavold@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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®