From owner-freebsd-current  Fri Feb 19  3: 4: 4 1999
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP id 69C1711664
	for <current@FreeBSD.ORG>; Fri, 19 Feb 1999 03:04:02 -0800 (PST)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id DAA31781;
	Fri, 19 Feb 1999 03:04:02 -0800 (PST)
	(envelope-from dillon)
Date: Fri, 19 Feb 1999 03:04:02 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199902191104.DAA31781@apollo.backplane.com>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: Julian Elischer <julian@whistle.com>,
	Kirk McKusick <mckusick@McKusick.COM>, Jake <jake@checker.org>,
	Don Lewis <Don.Lewis@tsc.tdk.com>, current@FreeBSD.ORG
Subject: Re: softupdate panic, anyone seen this? (fwd) 
References: <Pine.BSF.3.95.990218132053.16922A-100000@current1.whistle.com> <199902191043.CAA31641@apollo.backplane.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:    First, a couple of places where the worklist was not being protected
:    at splbio().  I'm not 100% sure that this is a problem but the code
:    is complex enough that it's just too dangerous not to do it.

    Ah... it *can* happen... brelse() can call brelvp() which can manipulate
    the dirtyblkhd/cleanblkhd and vn worklists.  brelse() can be called from
    an interrupt.  So, splbio() protection is mandatory.

						-Matt



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message