From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: 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>
Subject: Re: Default enable RCU list lockdep debugging with PROVE_RCU
Date: Thu, 14 May 2020 22:25:35 +1000 [thread overview]
Message-ID: <20200514222535.259cb69e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
Hi Paul,
This patch in the rcu tree
d13fee049fa8 ("Default enable RCU list lockdep debugging with PROVE_RCU")
is causing whack-a-mole in the syzbot testing of linux-next. Because
they always do a debug build of linux-next, no testing is getting done. :-(
Can we find another way to find all the bugs that are being discovered
(very slowly)?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-05-14 12:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:25 Stephen Rothwell [this message]
2020-05-14 12:31 ` Default enable RCU list lockdep debugging with PROVE_RCU 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
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=20200514222535.259cb69e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dvyukov@google.com \
--cc=frextrite@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).