[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <520385500.15226.1626181744332.JavaMail.zimbra@efficios.com>
Date: Tue, 13 Jul 2021 09:09:04 -0400 (EDT)
From: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
To: paulmck <paulmck@...nel.org>
Cc: zhouzhouyi@...il.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 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 ?
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
Powered by blists - more mailing lists