From owner-freebsd-bugs Tue May 9 11:30:46 2000 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 1FFB937BF61 for ; Tue, 9 May 2000 11:30:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA05016; Tue, 9 May 2000 11:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 9 May 2000 11:30:02 -0700 (PDT) Message-Id: <200005091830.LAA05016@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Jin Guojun (FTG staff) Subject: Re: kern/18471: Checking freeing of mbufs. Reply-To: Jin Guojun (FTG staff) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/18471; it has been noted by GNATS. From: Jin Guojun (FTG staff) To: FreeBSD-gnats-submit@FreeBSD.ORG, dwmalone@maths.tcd.ie Cc: Subject: Re: kern/18471: Checking freeing of mbufs. Date: Tue, 9 May 2000 11:29:55 -0700 (PDT) > It would be better if the kernel paniced at the time of the second > free, as opposed to some time later when the entry which has been > freed twice gets reused while still in use! I disagree to panic at this point. The better fixing is just printing out some error message and do nothing for refreeing code. Whoever writes such driver code will know what happens. -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message