From owner-freebsd-current Mon Nov 18 11:39: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC59037B401; Mon, 18 Nov 2002 11:39:01 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9090C43E42; Mon, 18 Nov 2002 11:39:01 -0800 (PST) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 6C906AE2C1; Mon, 18 Nov 2002 11:39:01 -0800 (PST) Date: Mon, 18 Nov 2002 11:39:01 -0800 From: Alfred Perlstein To: Kris Kennaway Cc: current@FreeBSD.org, tanimura@FreeBSD.org Subject: Re: Lock order reversals in sys_pipe.c and kern_sig.c Message-ID: <20021118193901.GA16066@elvis.mu.org> References: <20021118190819.GK12906@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021118190819.GK12906@rot13.obsecurity.org> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kris Kennaway [021118 11:06] wrote: > I've just turned witness back on on the bento cluster, and got the > following lock order reversals a number of times overnight: > > Nov 18 07:45:40 gohan11 kernel: 1st 0xc6887200 pipe mutex (pipe mutex) @ /local0/src-client/sys/kern/sys_pipe.c:465 > Nov 18 07:45:40 gohan11 kernel: 2nd 0xc0447780 sigio lock (sigio lock) @ /local0/src-client/sys/kern/kern_sig.c:2225 > Nov 18 10:28:47 gohan10 kernel: 1st 0xc4941580 pipe mutex (pipe mutex) @ /local0/src-client/sys/kern/sys_pipe.c:1038 > [...] > > Are these known problems? Well now they are, I will investigate as time permits. I'm still in a holding pattern about adding more debugging info to lockd now that we're in release candidate mode. I may ask for a branch to be done, but i'm not sure yet. thank you, -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message