Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754358AbcJEBC3 (ORCPT ); Tue, 4 Oct 2016 21:02:29 -0400 Received: from mx2.suse.de ([195.135.220.15]:34537 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753161AbcJEBC2 (ORCPT ); Tue, 4 Oct 2016 21:02:28 -0400 Date: Tue, 4 Oct 2016 18:02:14 -0700 From: Davidlohr Bueso To: Peter Zijlstra Cc: mingo@kernel.org, tglx@linutronix.de, juri.lelli@arm.com, rostedt@goodmis.org, xlpang@redhat.com, bigeasy@linutronix.de, linux-kernel@vger.kernel.org, mathieu.desnoyers@efficios.com, jdesfossez@efficios.com, bristot@redhat.com Subject: Re: [RFC][PATCH 0/4] FUTEX_UNLOCK_PI wobbles Message-ID: <20161005010214.GA32728@linux-80c1.suse> References: <20161003091234.879763059@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20161003091234.879763059@infradead.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 638 Lines: 23 On Mon, 03 Oct 2016, Peter Zijlstra wrote: > >Hi, > >During my last PI failing patch set it became obvious there's a number of >related fail in FUTEX_UNLOCK_PI that needed sorting before we can move on >with that stuff. > >These here patches are the result of staring at that code for a wee bit. > >Please have a very _very_ careful look at the last patch, it appears to not >explode when running: > > - perf bench futex lock-pi > - selftests/futex > >but given the immense amount of tricky involved with both PI and futex there is >bound to be something I've overlooked. > >Do people have more/better futex-pi test cases? pi_stress.