[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200305173953.GA10538@madhuparna-HP-Notebook>
Date: Thu, 5 Mar 2020 23:09:54 +0530
From: Madhuparna Bhowmik <madhuparnabhowmik10@...il.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: madhuparnabhowmik10@...il.com, paulmck@...nel.org,
josh@...htriplett.org, rostedt@...dmis.org,
mathieu.desnoyers@...icios.com, jiangshanlai@...il.com,
joel@...lfernandes.org, linux-kernel@...r.kernel.org,
Amol Grover <frextrite@...il.com>
Subject: Re: [PATCH] Default enable RCU list lockdep debugging with PROVE_RCU
On Thu, Mar 05, 2020 at 07:52:38AM -0800, Guenter Roeck wrote:
> On Fri, Feb 28, 2020 at 02:54:51PM +0530, madhuparnabhowmik10@...il.com wrote:
> > From: Madhuparna Bhowmik <madhuparnabhowmik10@...il.com>
> >
> > This patch default enables CONFIG_PROVE_RCU_LIST option with
> > CONFIG_PROVE_RCU for RCU list lockdep debugging.
> >
> > With this change, RCU list lockdep debugging will be default
> > enabled in CONFIG_PROVE_RCU=y kernels.
> >
> > Most of the RCU users (in core kernel/, drivers/, and net/
> > subsystem) have already been modified to include lockdep
> > expressions hence RCU list debugging can be enabled by
> > default.
> >
> > However, there are still chances of enountering
> > false-positive lockdep splats because not everything is converted,
> > in case RCU list primitives are used in non-RCU read-side critical
> > section but under the protection of a lock. It would be okay to
> > have a few false-positives, as long as bugs are identified, since this
> > patch only affects debugging kernels.
> >
> > Co-developed-by: Amol Grover <frextrite@...il.com>
> > Signed-off-by: Amol Grover <frextrite@...il.com>
> > Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik10@...il.com>
>
> Who is going to fix the fallout ?
>
> fs/btrfs/block-group.c:2011 RCU-list traversed in non-reader section!!
> kernel/kprobes.c:329 RCU-list traversed in non-reader section!!
> net/ipv4/ipmr.c:136 RCU-list traversed in non-reader section!!
>
Hi,
There is already a patch for fixing the warnings in kernel/kprobes.c :
https://lore.kernel.org/lkml/157905963533.2268.4672153983131918123.stgit@devnote2/
Same for net/ipv4/ipmr:
https://lore.kernel.org/patchwork/patch/1198934/
Can you please send the warning with the stack backtrace and locks held
for btrfs/block-group.c, I will work on it.
Thank you,
Madhuparna
> This is just from my boot tests. I'll keep PROVE_RCU enabled for the
> time being, but unless the noise is addressed I'll have to disable it
> because otherwise the real problems disappear in the noise.
>
> Guenter
Powered by blists - more mailing lists