From owner-freebsd-current Mon Oct 21 20:39:29 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 4FEA437B401 for ; Mon, 21 Oct 2002 20:39:28 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5C5A43E42 for ; Mon, 21 Oct 2002 20:39:27 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.4/8.12.4) with SMTP id g9M3coOo007484; Mon, 21 Oct 2002 23:38:50 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 21 Oct 2002 23:38:50 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Lars Eggert Cc: current Subject: Re: yet another lock order reversal In-Reply-To: <3DB49629.4090302@isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Mon, 21 Oct 2002, Lars Eggert wrote: > lock order reversal > 1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465 > 2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156 It strikes me that, for better or for worse, the reported "reversal" is the right way around, and the prior access was the wrong one. It may be possible to extract the locking locations of the prior order using 'show witness' in ddb. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message