From owner-freebsd-current Tue Dec 1 19:11:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26820 for freebsd-current-outgoing; Tue, 1 Dec 1998 19:11:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp3.portal.net.au [202.12.71.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26815 for ; Tue, 1 Dec 1998 19:10:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA02126; Tue, 1 Dec 1998 19:08:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812020308.TAA02126@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John Saunders" cc: "Garrett Wollman" , "Matthew Dillon" , freebsd-current@FreeBSD.ORG Subject: Re: D.O.S. attack protection enhancements commit (ICMP_BANDLIM) In-reply-to: Your message of "Wed, 02 Dec 1998 13:58:43 +1100." <002401be1d9f$ac2c1bd0$6cb611cb@saruman.scitec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Dec 1998 19:08:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If the problem is mbuf starvation shouldn't the network layer > simply pause until resources become available? Anything not > network related should continue as normal. This is probably the single most insidious problem that our stack currently faces; portions of the code assume that mbuf allocation will always succeed. These code portions require redesign, often nontrivial, to allow them to abort in one fashion or another when allocation fails. We've presented this situation to plaintiffs a number of times; we haven't received any code back yet. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message