[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNOJYWjhK3Z=mbbum8V8WzWOyfTWqz--+C3Z08LPCWm2Rw@mail.gmail.com>
Date: Thu, 21 May 2020 11:37:54 +0200
From: Marco Elver <elver@...gle.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Will Deacon <will@...nel.org>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-tip-commits@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>, x86 <x86@...nel.org>
Subject: Re: [tip: locking/kcsan] READ_ONCE: Use data_race() to avoid KCSAN instrumentation
On Thu, 21 May 2020 at 09:26, Borislav Petkov <bp@...en8.de> wrote:
>
> On Thu, May 21, 2020 at 12:30:39AM +0200, Marco Elver wrote:
> > This should be fixed when the series that includes this commit is applied:
> > https://lore.kernel.org/lkml/20200515150338.190344-9-elver@google.com/
>
> Yap, that fixes it.
>
> Thx.
Thanks for confirming. I think Peter also mentioned that nested
statement expressions caused issues.
This probably also means we shouldn't have a nested "data_race()"
macro, to avoid any kind of nested statement expressions where
possible.
I will send a v2 of the above series to add that patch.
Thanks,
-- Marco
Powered by blists - more mailing lists