From owner-freebsd-bugs Thu Sep 30 0:49: 2 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from neo.gen.oleane.fr (neo.gen.oleane.fr [194.2.203.96]) by hub.freebsd.org (Postfix) with ESMTP id EB703151C6; Thu, 30 Sep 1999 00:48:59 -0700 (PDT) (envelope-from spe@oleane.net) Received: by neo.gen.oleane.fr (Postfix, from userid 0) id D9406995E0; Thu, 30 Sep 1999 09:52:37 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by neo.gen.oleane.fr (Postfix) with ESMTP id D74FC993CD; Thu, 30 Sep 1999 09:52:37 +0200 (CEST) Date: Thu, 30 Sep 1999 09:52:37 +0200 (CEST) From: Sebastien Petit To: dillon@FreeBSD.org Cc: spe@oleane.net, freebsd-bugs@FreeBSD.org Subject: Re: kern/13488: panic: getnewbuf: In-Reply-To: <199909291702.KAA69616@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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. Yes, good, I try the bug of getnewbuf on 3.3-RELEASE and It doesn't crash. Thanks for your patch and your good work. Sebastien. --- spe@oleane.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message