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  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:   Wed, 5 Jun 2019 23:05:11 -0700
From:   "Paul E. McKenney" <>
To:     Herbert Xu <>
Cc:     Alan Stern <>,
        Boqun Feng <>,
        Linus Torvalds <>,
        Frederic Weisbecker <>,
        Fengguang Wu <>, LKP <>,
        LKML <>,
        Netdev <>,
        "David S. Miller" <>,
        Andrea Parri <>,
        Luc Maranget <>,
        Jade Alglave <>
Subject: Re: rcu_read_lock lost its compiler barrier

On Thu, Jun 06, 2019 at 12:51:09PM +0800, Herbert Xu wrote:
> On Tue, Jun 04, 2019 at 10:44:18AM -0400, Alan Stern wrote:
> >
> > Currently the LKMM says the test is allowed and there is a data race, 
> > but this answer clearly is wrong since it would violate the RCU 
> > guarantee.
> Thank you! This is what I tried to say all along in this thread
> but you expressed it in a much better way :)

In case you were wondering, the reason that I was giving you such
a hard time was that from what I could see, you were pushing for no
{READ,WRITE}_ONCE() at all.  ;-)

							Thanx, Paul

Powered by blists - more mailing lists