From: Joel Fernandes <joelagnelf@nvidia.com>
To: Cunlong Li <shenxiaogll@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.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>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rcu@vger.kernel.org" <rcu@vger.kernel.org>
Subject: Re: [PATCH] rcu: Enable runtime reset of the RCU stall panic count
Date: Tue, 6 Oct 2026 17:27:51 -0400 [thread overview]
Message-ID: <53383f19-3d54-405b-85af-f597b69befe6@nvidia.com> (raw)
In-Reply-To: <asT08QHOiIJrfIIZ@63b45mr6s164qmn>
On 10/6/2026 9:17 AM, Cunlong Li wrote:
>> It sounds like you do know that it is likely transient - but based on this description and the below, it sounds like you have not yet found a use of this patch.
>>
>>
> To be precise, we worry that some of the stalls were transient, so a
> panic reboot would affect the users. But we have no hard evidence
> either way: every incident ended in a forced reset, and the dmesg was
> lost. Going forward, we plan to enable the NMI and kdump to keep
> investigating the cause of the RCU stalls. We will also monitor dmesg
> to confirm whether transient RCU stalls actually occur.
Right, I just worry that if you're not seeing recoverable/transient stalls and
you start using this patch, then you might be causing side-effects that don't
really help your problem and might be masking the real issue. It would be good
to debug this further, and fix the right way IMO.
If you show that this patch indeed helps your problem, we can consider it for
7.5, but there's little bit of time. :-)
Thanks,
Joel Fernandes
prev parent reply other threads:[~2026-10-06 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 1:14 Cunlong Li
2026-10-04 11:04 ` Bradley Morgan
2026-10-05 12:56 ` Joel Fernandes
2026-10-06 11:54 ` Cunlong Li
2026-10-06 12:21 ` Joel Fernandes
2026-10-06 12:39 ` Joel Fernandes
2026-10-06 13:17 ` Cunlong Li
2026-10-06 21:27 ` Joel Fernandes [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=53383f19-3d54-405b-85af-f597b69befe6@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=boqun@kernel.org \
--cc=corbet@lwn.net \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.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=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shenxiaogll@gmail.com \
--cc=skhan@linuxfoundation.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®