Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751878AbdIAJ6P (ORCPT ); Fri, 1 Sep 2017 05:58:15 -0400 Received: from mail-pg0-f68.google.com ([74.125.83.68]:37599 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751759AbdIAJ6O (ORCPT ); Fri, 1 Sep 2017 05:58:14 -0400 X-Google-Smtp-Source: ADKCNb6FWKg795nS7xNBB2o2G1XUxXFStXUA/wh2Jp7O4mRumoxVPfAn9PHQlUr5IjndLUVB+fSogg== Date: Fri, 1 Sep 2017 19:55:29 +1000 From: Nicholas Piggin To: Andrea Parri Cc: Ingo Molnar , Peter Zijlstra , Paul McKenney , Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: [PATCH] swait: add missing barrier to swake_up Message-ID: <20170901195529.6edca064@roar.ozlabs.ibm.com> In-Reply-To: <20170901092322.GA4192@andrea> References: <20170901061450.1450-1-npiggin@gmail.com> <20170901092322.GA4192@andrea> Organization: IBM X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1366 Lines: 36 On Fri, 1 Sep 2017 11:23:22 +0200 Andrea Parri wrote: > On Fri, Sep 01, 2017 at 04:14:50PM +1000, Nicholas Piggin wrote: > > swake_up and swake_up_all test the swaitqueue outside the lock, > > but they are missing the barrier that would ensure visibility > > of a previous store that sets the wakeup condition with the > > load that tests the swaitqueue. This could lead to a lost wakeup > > if there is memory reordering. Fix this as prescribed by the > > waitqueue_active comments. > > > > Signed-off-by: Nicholas Piggin > > -- > > I noticed this when chasing down that rcu hang bug (which > > turned out to not be anything of the sort). I might be missing > > something here and it's safe somehow, but if so then it should > > have a comment where it diverges from normal waitqueues. > > > > It looks like there's a few callers which are also testing > > swait_active before swake_up without a barrier which look wrong, > > so I must be missing something but I'm not sure what. > > Hi Nicholas. I noticed > > 35a2897c2a306cca344ca5c0b43416707018f434 > ("sched/wait: Remove the lockless swait_active() check in swake_up*()") > > in tip:locking/core. Oh thanks, I missed that. Should be in 4.14/stable IMO. As I said as well, several callers have picked up bad habits. RCU looks okay though. Thanks, Nick