From: Oliver Sang <oliver.sang@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: [paulmck-rcu:dev.2023.11.08a] [EXP locktorture] 1254a620b4: WARNING:at_kernel/rcu/tree_stall.h:#rcu_stall_chain_notifier_register
Date: Tue, 12 Dec 2023 10:06:36 +0800 [thread overview]
Message-ID: <ZXfALH1TIHSH/7cN@xsang-OptiPlex-9020> (raw)
In-Reply-To: <2ad1abcc-d82b-406f-a7b7-606224a24813@paulmck-laptop>
hi, Paul,
On Mon, Dec 11, 2023 at 08:59:16AM -0800, Paul E. McKenney wrote:
> On Thu, Dec 07, 2023 at 04:19:56PM +0800, kernel test robot wrote:
> >
> >
> > Hello,
> >
> > kernel test robot noticed "WARNING:at_kernel/rcu/tree_stall.h:#rcu_stall_chain_notifier_register" on:
> >
> > commit: 1254a620b4a3832e65ac01bcef769b99e34515b2 ("EXP locktorture: Add RCU CPU stall-warning notifier stub")
> > https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git dev.2023.11.08a
>
> Thank you for your testing efforts!
>
> This one is expected behavior by explicit request from Linus Torvalds.
> The concern is that people might use this hook without understanding
> the risks of losing RCU CPU stall warnings.
>
> One fix would be to never specify the rcupdate.rcu_cpu_stall_notifiers
> kernel boot parameter. Another would be to forgive this warning when
> that boot parameter was specified. Your choice! ;-)
>
> Thanx, Paul
Thanks a lot for information!
this commit (1254a620b4) is a test for this warning, am I right?
when this warning mechanism goes into upstream, do you want us still report
for similar cases? or we could just ignore them? Thanks!
next prev parent reply other threads:[~2023-12-12 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 8:19 kernel test robot
2023-12-11 16:59 ` Paul E. McKenney
2023-12-12 2:06 ` Oliver Sang [this message]
2023-12-12 4:26 ` Paul E. McKenney
2023-12-12 7:43 ` Oliver Sang
2023-12-12 14:43 ` Paul E. McKenney
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=ZXfALH1TIHSH/7cN@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=paulmck@kernel.org \
/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®