From owner-freebsd-security Sun Jan 23 17:53:22 2000 Delivered-To: freebsd-security@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 41F6614D82 for ; Sun, 23 Jan 2000 17:53:17 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115220>; Mon, 24 Jan 2000 12:53:51 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: kernel panic's still due to mbuf problems. In-reply-to: <200001232329.KAA02494@cairo.anu.edu.au>; from avalon@coombs.anu.edu.au on Mon, Jan 24, 2000 at 10:30:39AM +1100 To: Darren Reed Cc: freebsd-security@FreeBSD.ORG Message-Id: <00Jan24.125351est.115220@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200001232329.KAA02494@cairo.anu.edu.au> Date: Mon, 24 Jan 2000 12:53:49 +1100 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2000-Jan-24 10:30:39 +1100, Darren Reed wrote: >Amongst all these `stream.c' emails, I noticed at least one which >had a FreeBSD panic message saying there were no mbuf's free. I >think it was for a 3.4 system. *That* is the bug which should be >fixed. Unfortunately, your patches to do so seem to have become separated from your posting :-). This subject has been discussed regularly and so far, no-one has managed to produce a solution which does not entail a significant performance hit. It's generally accepted that the current behaviour is undesirable and if you have real solution to offer, I'm sure it'll be gratefully accepted. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message