Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751569AbaJRQPg (ORCPT ); Sat, 18 Oct 2014 12:15:36 -0400 Received: from mail-lb0-f181.google.com ([209.85.217.181]:34942 "EHLO mail-lb0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751408AbaJRQPf (ORCPT ); Sat, 18 Oct 2014 12:15:35 -0400 Message-ID: <1413648929.5367.25.camel@marge.simpson.net> Subject: Re: [PATCH] futex: Ensure get_futex_key_refs() always implies a barrier From: Mike Galbraith To: Linus Torvalds Cc: Catalin Marinas , Linux Kernel Mailing List , Matteo Franchin , Davidlohr Bueso , Darren Hart , Thomas Gleixner , Peter Zijlstra , Ingo Molnar , "Paul E. McKenney" Date: Sat, 18 Oct 2014 18:15:29 +0200 In-Reply-To: References: <1413563929-2664-1-git-send-email-catalin.marinas@arm.com> <1413615285.5741.41.camel@marge.simpson.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2014-10-18 at 08:28 -0700, Linus Torvalds wrote: > On Fri, Oct 17, 2014 at 11:54 PM, Mike Galbraith > wrote: > > > > The barrier fixing up my problematic box smells a lot like evidence. > > Is this a "tested-by"? Did you actuallyu verify that the patch ends up > fixing the problem you saw? Yup, it definitely fixed it up. Weird that it didn't show at all on the 2 socket 20 core box the problem I was looking into was reported on, but was 100% busted on the similar 2 socket 28 core box I borrowed to have a peek, and only that box. My (crippled/slow) 64 core DL980 was perfectly happy, as were my 3 home boxen, not a peep from anywhere but that one 28 core box. Hohum.. Tested-by: Mike Galbraith -Mike -- 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/