From: "Paul E. McKenney" <paulmck@kernel.org>
To: Qian Cai <cai@lca.pw>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>,
Amol Grover <frextrite@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
philip.li@intel.com, lkp@intel.com, fengguang.wu@intel.com,
rong.a.chen@intel.com
Subject: Re: Default enable RCU list lockdep debugging with PROVE_RCU
Date: Sun, 17 May 2020 14:47:16 -0700 [thread overview]
Message-ID: <20200517214716.GT2869@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <CA610F47-290E-4826-B1D9-7CE09D7CEA6D@lca.pw>
On Fri, May 15, 2020 at 02:36:26PM -0400, Qian Cai wrote:
>
>
> > On May 14, 2020, at 2:13 PM, Paul E. McKenney <paulmck@kernel.org> wrote:
> >
> > Fair enough! And yes, the Linux kernel is quite large, so I certainly am
> > not asking you to test the whole thing yourself.
>
> Ok, I saw 0day bot also started to report those which is good. For example,
>
> lkml.org/lkml/2020/5/12/1358
>
> which so far is nit blocking 0day on linux-next since it does not use panic_on_warn yet (while syzbot does).
>
> Thus, I am more convinced that we should not revert the commit just for syzbot until someone could also convince 0day to select RCU_EXPERT and then DEBUG_RCU_LIST?
Let's ask the 0day people, now CCed, if they would be willing to
build with CONFIG_RCU_EXPERT=y and CONFIG_DEBUG_RCU_LIST=y on some
fraction of their testing. ;-)
Thanx, Paul
next prev parent reply other threads:[~2020-05-17 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:25 Default enable RCU list lockdep debugging with PROVE_RCU Stephen Rothwell
2020-05-14 12:31 ` Qian Cai
2020-05-14 13:33 ` Paul E. McKenney
2020-05-14 13:39 ` Qian Cai
2020-05-14 13:44 ` Qian Cai
2020-05-14 13:54 ` Paul E. McKenney
2020-05-14 14:03 ` Qian Cai
2020-05-14 15:34 ` Paul E. McKenney
2020-05-14 15:46 ` Qian Cai
2020-05-14 18:13 ` Paul E. McKenney
2020-05-15 18:36 ` Qian Cai
2020-05-17 21:47 ` Paul E. McKenney [this message]
2020-05-18 5:54 ` Rong Chen
2020-05-18 12:44 ` 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=20200517214716.GT2869@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=cai@lca.pw \
--cc=dvyukov@google.com \
--cc=fengguang.wu@intel.com \
--cc=frextrite@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkp@intel.com \
--cc=madhuparnabhowmik10@gmail.com \
--cc=philip.li@intel.com \
--cc=rong.a.chen@intel.com \
--cc=sfr@canb.auug.org.au \
/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