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:   Fri, 15 May 2020 16:07:20 +0200
From:   Peter Zijlstra <>
To:     David Laight <David.Laight@...LAB.COM>
Cc:     Marco Elver <>, Will Deacon <>,
        kasan-dev <>,
        LKML <>,
        Thomas Gleixner <>,
        "Paul E. McKenney" <>,
        Ingo Molnar <>,
        Dmitry Vyukov <>
Subject: Re: [PATCH v5 00/18] Rework READ_ONCE() to improve codegen

On Fri, May 15, 2020 at 01:55:43PM +0000, David Laight wrote:
> From: Peter Zijlstra
> > Sent: 14 May 2020 15:25
> ..
> > Exact same requirements, KASAN even has the data_race() problem through
> > READ_ONCE_NOCHECK(), UBSAN doesn't and might be simpler because of it.
> What happens if you implement READ_ONCE_NOCHECK() with an
> asm() statement containing a memory load?
> Is that enough to kill all the instrumentation?

You'll have to implement it for all archs, but yes, I think that ought
to work.

Powered by blists - more mailing lists