Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753290AbbBMPnQ (ORCPT ); Fri, 13 Feb 2015 10:43:16 -0500 Received: from mx1.redhat.com ([209.132.183.28]:54534 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752811AbbBMPnP (ORCPT ); Fri, 13 Feb 2015 10:43:15 -0500 Date: Fri, 13 Feb 2015 16:40:02 +0100 From: Oleg Nesterov To: Raghavendra K T Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, peterz@infradead.org, torvalds@linux-foundation.org, konrad.wilk@oracle.com, pbonzini@redhat.com, paulmck@linux.vnet.ibm.com, waiman.long@hp.com, davej@redhat.com, x86@kernel.org, jeremy@goop.org, paul.gortmaker@windriver.com, ak@linux.intel.com, jasowang@redhat.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, xen-devel@lists.xenproject.org, riel@redhat.com, borntraeger@de.ibm.com, akpm@linux-foundation.org, a.ryabinin@samsung.com, sasha.levin@oracle.com, dave@stgolabs.net Subject: Re: [PATCH V4] x86 spinlock: Fix memory corruption on completing completions Message-ID: <20150213154002.GB9535@redhat.com> References: <1423809941-11125-1-git-send-email-raghavendra.kt@linux.vnet.ibm.com> <20150213153228.GA9535@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150213153228.GA9535@redhat.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1022 Lines: 28 On 02/13, Oleg Nesterov wrote: > > On 02/13, Raghavendra K T wrote: > > > > @@ -772,7 +773,8 @@ __visible void kvm_lock_spinning(struct arch_spinlock *lock, __ticket_t want) > > * check again make sure it didn't become free while > > * we weren't looking. > > */ > > - if (ACCESS_ONCE(lock->tickets.head) == want) { > > + head = READ_ONCE(lock->tickets.head); > > + if (__tickets_equal(head, want)) { > > add_stats(TAKEN_SLOW_PICKUP, 1); > > goto out; > > This is off-topic, but with or without this change perhaps it makes sense > to add smp_mb__after_atomic(). It is nop on x86, just to make this code > more understandable for those (for me ;) who can never remember even the > x86 rules. Not that I think you should do this in v5, so please ignore. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/