Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933574AbbDPKRB (ORCPT ); Thu, 16 Apr 2015 06:17:01 -0400 Received: from casper.infradead.org ([85.118.1.10]:41714 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933545AbbDPKQw (ORCPT ); Thu, 16 Apr 2015 06:16:52 -0400 Date: Thu, 16 Apr 2015 12:16:37 +0200 From: Peter Zijlstra To: Thomas Gleixner Cc: Davidlohr Bueso , Sebastian Andrzej Siewior , linux-kernel@vger.kernel.org, Ingo Molnar , Darren Hart , Steven Rostedt , fredrik.markstrom@windriver.com, Manfred Spraul , Arnaldo Carvalho de Melo Subject: Re: [PATCH 2/3 v2] futex: avoid double wake up in futex_wake() on -RT Message-ID: <20150416101637.GC5029@twins.programming.kicks-ass.net> References: <1428419030-20030-1-git-send-email-bigeasy@linutronix.de> <1428419030-20030-3-git-send-email-bigeasy@linutronix.de> <20150410161135.GF3057@linutronix.de> <1428894155.16668.6.camel@stgolabs.net> <1429160982.6795.35.camel@stgolabs.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 916 Lines: 22 On Thu, Apr 16, 2015 at 11:19:41AM +0200, Thomas Gleixner wrote: > So any code which does not handle a spurious wakeup is broken > independent of the futex changes. So really nothing to worry about. Back when we did this: http://lkml.iu.edu/hypermail/linux/kernel/1109.1/01941.html http://lkml.iu.edu/hypermail/linux/kernel/1109.1/01943.html Things came apart -- notably sysvsems. And yes its true that anything not dealing with spuriuos wakups is borken, but there's still quite a lot of borken out there, although I think we fixed all the really common ones. But if we decide we want to go do this, I'd propose we reintroduce this delayed wake list thing again. -- 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/