From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754064AbcIBWRD (ORCPT ); Fri, 2 Sep 2016 18:17:03 -0400 Received: from merlin.infradead.org ([205.233.59.134]:52982 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752269AbcIBWRB (ORCPT ); Fri, 2 Sep 2016 18:17:01 -0400 Date: Sat, 3 Sep 2016 00:16:58 +0200 From: Peter Zijlstra To: Alan Stern Cc: "Paul E. McKenney" , Ingo Molnar , Felipe Balbi , USB list , Kernel development list Subject: Re: Memory barrier needed with wake_up_process()? Message-ID: <20160902221658.GO10153@twins.programming.kicks-ass.net> References: <20160902191857.GL10153@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 02, 2016 at 04:16:54PM -0400, Alan Stern wrote: > Felipe, your tests will show whether my guess was totally off-base. > For the new people, Felipe is tracking down a problem that involves > exactly the code sequence listed at the top of the email, where we know > that the wakeup routine runs but nevertheless the task sleeps. At > least, that's what it looks like at the moment. What arch are you seeing this on?