Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
From:   Qian Cai <cai@lca.pw>
Mime-Version: 1.0 (1.0)
Subject: Re: Default enable RCU list lockdep debugging with PROVE_RCU
Date:   Fri, 15 May 2020 14:36:26 -0400
Message-Id: <CA610F47-290E-4826-B1D9-7CE09D7CEA6D@lca.pw>
References: <20200514181305.GT2869@paulmck-ThinkPad-P72>
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>
In-Reply-To: <20200514181305.GT2869@paulmck-ThinkPad-P72>
To:     paulmck@kernel.org
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On May 14, 2020, at 2:13 PM, Paul E. McKenney <paulmck@kernel.org> wrote:
>=20
> 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 syzb=
ot until someone could also convince 0day to select RCU_EXPERT and then DEBU=
G_RCU_LIST?=