From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trond Myklebust Subject: Re: Fw: Spam: [Bugme-new] [Bug 2829] New: posix_locks_deadlock() loops infinitely Date: Fri, 04 Jun 2004 23:47:21 -0400 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1086407241.6959.43.camel@lade.trondhjem.org> References: <200406050329.i553TprK011740@supreme.pcug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Andrew Morton , willy@debian.org, linux-fsdevel@vger.kernel.org Return-path: Received: from dh132.citi.umich.edu ([141.211.133.132]:3981 "EHLO lade.trondhjem.org") by vger.kernel.org with ESMTP id S264524AbUFEDrZ convert rfc822-to-8bit (ORCPT ); Fri, 4 Jun 2004 23:47:25 -0400 To: Stephen Rothwell In-Reply-To: <200406050329.i553TprK011740@supreme.pcug.org.au> List-Id: linux-fsdevel.vger.kernel.org P=E5 fr , 04/06/2004 klokka 23:29, skreiv Stephen Rothwell: > From: Andrew Morton > > > > (How can we simply rip it? Isn't it trying to do something useful?= ) >=20 > I used to think so, but Andrew Tridgell convinced me that since it > actually returns false positives and false negatives in the presence = of > threads, all we are really doing is trying to paper over user mode > programming errors ... So you are saying that extending a lock is basically a programming error? Trond - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html