Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964891AbWBCDTB (ORCPT ); Thu, 2 Feb 2006 22:19:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964893AbWBCDTB (ORCPT ); Thu, 2 Feb 2006 22:19:01 -0500 Received: from wproxy.gmail.com ([64.233.184.200]:10942 "EHLO wproxy.gmail.com") by vger.kernel.org with ESMTP id S964891AbWBCDTA convert rfc822-to-8bit (ORCPT ); Thu, 2 Feb 2006 22:19:00 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QmIn4oHjKPKuMcd5XPcjU0YJ/6G9HxshL6+Uvf1yxrKA+mt7KcnIslgOCjswt2sp9+i896S92qC+43/lhN6goEvajaMq5+0o0N5QXUBO5SZ7lYZOP8F6m9rGBVnobX5m0k/jyFq+tM2avuAMwlvGEsUhgrQAgoOMIOmY2fwAss4= Message-ID: Date: Thu, 2 Feb 2006 19:18:59 -0800 From: David Singleton To: tglx@linutronix.de, mingo@elte.hu Subject: Re: Robust mutexes (-rt) Cc: linux-kernel@vger.kernel.org In-Reply-To: <1138909303.29087.51.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Content-Disposition: inline References: <1138740179.5184.34.camel@localhost.localdomain> <1138863989.29087.24.camel@localhost.localdomain> <1138909303.29087.51.camel@localhost.localdomain> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1164 Lines: 35 Thomas, here is a patch that fixes the -EINTR problem and a fix for Dinakar's simple futex deadlock test program. When Esben's new deadlock detection is ready I plan to use it for robust futex deadlock detection, both simple and circular deadlock detection. http://source.mvista.com:~dsingleton/patch-2.6.15-rt16-rf1 include/linux/futex.h | 3 +++ kernel/futex.c | 3 +++ kernel/rt.c | 19 ++++++++++++++++++- 3 files changed, 24 insertions(+), 1 deletion(-) David > Just another problem: > > pthread_mutex_lock() of a robust mutex returns -EINTR, which is wrong by > the specification. We encountered this in an application. Not sure what > to do about that. It needs either a fix in glibc or the kernel could > handle it via a restart function. That happens when a signal is > delivered to the thread while the thread is blocked on the mutex. > > tglx > > > > > - 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/