lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 17 May 2020 14:47:16 -0700
From:   "Paul E. McKenney" <>
To:     Qian Cai <>
Cc:     Stephen Rothwell <>,
        Linux Next Mailing List <>,
        Linux Kernel Mailing List <>,
        Madhuparna Bhowmik <>,
        Amol Grover <>,
        Dmitry Vyukov <>,,,,
Subject: Re: Default enable RCU list lockdep debugging with PROVE_RCU

On Fri, May 15, 2020 at 02:36:26PM -0400, Qian Cai wrote:
> > On May 14, 2020, at 2:13 PM, Paul E. McKenney <> 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,
> 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

Powered by blists - more mailing lists