From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Rutland Subject: Re: [PATCH 0/3] virtio/vringh: kill off ACCESS_ONCE() Date: Fri, 25 Nov 2016 18:07:03 +0000 Message-ID: <20161125180649.GC30811@leverpostej> References: <32dfca07-59f3-b75a-3154-cf6b6c8538f0@de.ibm.com> <20161125122356.GB26611@leverpostej> <20161125124044.GN3092@twins.programming.kicks-ass.net> <20161125124404.GI3174@twins.programming.kicks-ass.net> <20161125145512.GA4014@Boquns-MacBook-Pro.local> <20161125161004.GA30181@leverpostej> <20161125161709.GQ3092@twins.programming.kicks-ass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dmitry Vyukov , Peter Zijlstra , Boqun Feng , Christian Borntraeger , "Michael S. Tsirkin" , LKML , Davidlohr Bueso , Davidlohr Bueso , Jason Wang , KVM list , netdev , Paul McKenney , virtualization To: Linus Torvalds Return-path: Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Fri, Nov 25, 2016 at 09:52:50AM -0800, Linus Torvalds wrote: > READ/WRITE_ONCE() are atomic *WHEN*THAT*IS*POSSIBLE*. > But sometimes it's not going to be atomic. That's the problem. Common code may rely on something being atomic when that's only true on a subset of platforms. On others, it's silently "fixed" into something that isn't atomic, and we get no diagnostic. The bug lurks beneath the surface. Thanks, Mark.