[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAABZP2zO6WpaYW33V_Di5naxr1TRm0tokCmTZahDuXmRupxd=A@mail.gmail.com>
Date: Wed, 14 Jul 2021 12:44:36 +0800
From: Zhouyi Zhou <zhouzhouyi@...il.com>
To: paulmck@...nel.org
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Josh Triplett <josh@...htriplett.org>,
rostedt <rostedt@...dmis.org>,
Lai Jiangshan <jiangshanlai@...il.com>,
"Joel Fernandes, Google" <joel@...lfernandes.org>,
rcu <rcu@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] RCU: Fix macro name CONFIG_TASKS_RCU_TRACE
On Tue, Jul 13, 2021 at 11:19 PM Paul E. McKenney <paulmck@...nel.org> wrote:
>
> On Tue, Jul 13, 2021 at 06:18:12AM -0700, Paul E. McKenney wrote:
> > On Tue, Jul 13, 2021 at 09:09:04AM -0400, Mathieu Desnoyers wrote:
> > > ----- On Jul 13, 2021, at 12:16 AM, paulmck paulmck@...nel.org wrote:
> > >
> > > > On Tue, Jul 13, 2021 at 08:56:45AM +0800, zhouzhouyi@...il.com wrote:
> > > >> From: Zhouyi Zhou <zhouzhouyi@...il.com>
> > > >>
> > > >> Hi Paul,
> > > >>
> > > >> During my studying of RCU, I did a grep in the kernel source tree.
> > > >> I found there are 3 places where the macro name CONFIG_TASKS_RCU_TRACE
> > > >> should be CONFIG_TASKS_TRACE_RCU instead.
> > > >>
> > > >> Without memory fencing, the idle/userspace task inspection may not
> > > >> be so accurate.
> > > >>
> > > >> Thanks for your constant encouragement for my studying.
> > > >>
> > > >> Best Wishes
> > > >> Zhouyi
> > > >>
> > > >> Signed-off-by: Zhouyi Zhou <zhouzhouyi@...il.com>
> > > >
> > > > Good eyes, and those could cause real bugs, so thank you!
> > >
> > > Hi Paul,
> > >
> > > This makes me wonder: what is missing testing-wise in rcutorture to
> > > catch those issues with testing before they reach mainline ?
> >
> > My guess: Running on weakly ordered architectures. ;-)
>
> And another guess: A tool that identifies use of Kconfig options
> that are not defined in any Kconfig* file.
Based on Paul's second guess ;-), I did a small research, and I think
the best answer is to modify scripts/checkpatch.pl. We modify checkpatch.pl
to identify use of Kconfig options that are not defined in any Kconfig* file.
As I am a C/C++ programmer, I would be glad to take some time to learn
perl (checkpatch is implented in perl) first if no other volunteer is
about to do it ;-)
>
> Thanx, Paul
Thanx
Zhouyi
Powered by blists - more mailing lists