From owner-freebsd-stable@FreeBSD.ORG Tue Aug 16 12:22:45 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18F7616A41F for ; Tue, 16 Aug 2005 12:22:45 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FA4F43D46 for ; Tue, 16 Aug 2005 12:22:44 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 829976193; Tue, 16 Aug 2005 14:22:26 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id 72025617D; Tue, 16 Aug 2005 14:22:26 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 30E7933D38; Tue, 16 Aug 2005 14:22:38 +0200 (CEST) To: Garry Belka References: <42F3DC53.1060506@networkphysics.com> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Tue, 16 Aug 2005 14:22:38 +0200 In-Reply-To: <42F3DC53.1060506@networkphysics.com> (Garry Belka's message of "Fri, 05 Aug 2005 14:38:27 -0700") Message-ID: <86vf26kr5d.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Tests: ALL_TRUSTED,AWL,BAYES_00 X-Spam-Learn: ham X-Spam-Score: -5.3/5.0 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on tim.des.no Cc: freebsd-stable@freebsd.org Subject: Re: 5.4-STABLE panic in propagate_priority() and a tentative patch X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2005 12:22:45 -0000 Garry Belka writes: > We saw several panics of the same kind on different systems running > 5.4-STABLE. The panic was in propagate_priority() and was ultimately > traced to vget() call in pfs_vncache_alloc(). vget() is called under > global pfs mutex. When vget() sleeps, propagate_priority() in a > different thread comes across a sleeping thread that owns a blocked > mutex, and that causes a panic. Could you please file a PR about this issue, with the patch attached? (use 'send-pr -a /path/to/patch' to avoid clobbering whitespace) DES --=20 Dag-Erling Sm=F8rgrav - des@des.no