From owner-freebsd-bugs  Wed Sep 29 10: 3: 6 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 385F415958; Wed, 29 Sep 1999 10:02:17 -0700 (PDT)
	(envelope-from dillon@FreeBSD.org)
Received: (from dillon@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id KAA69616;
	Wed, 29 Sep 1999 10:02:16 -0700 (PDT)
	(envelope-from dillon@FreeBSD.org)
Date: Wed, 29 Sep 1999 10:02:16 -0700 (PDT)
From: <dillon@FreeBSD.org>
Message-Id: <199909291702.KAA69616@freefall.freebsd.org>
To: spe@oleane.net, dillon@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: kern/13488: panic: getnewbuf:
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: panic: getnewbuf:

State-Changed-From-To: open->closed
State-Changed-By: dillon
State-Changed-When: Wed Sep 29 10:00:27 PDT 1999
State-Changed-Why: 
Just prior to the 3.3 release getnewbuf() was patched to avoid this particular
panic.  The patch is about as good as we can get short of rewriting 
getnewbuf() in the 3.x releases.  getnewbuf() *has* been completely rewritten
in the 4.x development kernels (i.e. -current) and does not have this problem
at all.


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