From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965572AbcBDJHk (ORCPT ); Thu, 4 Feb 2016 04:07:40 -0500 Received: from www.linutronix.de ([62.245.132.108]:35563 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965211AbcBDJHg (ORCPT ); Thu, 4 Feb 2016 04:07:36 -0500 Date: Thu, 4 Feb 2016 10:06:11 +0100 (CET) From: Thomas Gleixner To: Davidlohr Bueso cc: Mel Gorman , Peter Zijlstra , Ingo Molnar , Sebastian Andrzej Siewior , Chris Mason , Darren Hart , Hugh Dickins , linux-kernel@vger.kernel.org, Davidlohr Bueso , Mel Gorman Subject: Re: [PATCH v5] futex: Remove requirement for lock_page in get_futex_key In-Reply-To: <1454567326-16114-1-git-send-email-dave@stgolabs.net> Message-ID: References: <1454567326-16114-1-git-send-email-dave@stgolabs.net> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 3 Feb 2016, Davidlohr Bueso wrote: > + * We are not calling into get_futex_key_refs() in file-backed > + * cases, therefore a successful atomic_inc return below will > + * guarantee that get_futex_key() will continue to imply MB (B). Can you please make that "MB (B)" part a bit more outstanding. I really had to search for it. > + */ > + if (WARN_ON_ONCE(!atomic_inc_not_zero(&inode->i_count))) { > + rcu_read_unlock(); > + put_page(page); > + > + goto again; > + } Don't we need smp_mb__after_atomic(); here to make it a full barrier on all architectures? Thanks, tglx