From owner-freebsd-stable@FreeBSD.ORG Thu Jun 26 18:15:59 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AF5737B401 for ; Thu, 26 Jun 2003 18:15:59 -0700 (PDT) Received: from smtp1.home.se (smtp1.home.se [213.214.194.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DD4644003 for ; Thu, 26 Jun 2003 18:15:58 -0700 (PDT) (envelope-from sandos@home.se) Received: from sandos sandos@home.se [130.243.95.28]Novell NetWare; Fri, 27 Jun 2003 03:14:58 +0200 Message-ID: <001301c33c49$ae39ab40$0000fea9@sandos> From: =?iso-8859-1?Q?John_B=E4ckstrand?= To: "Eugene Grosbein" References: <000b01c33b7e$bc37fdd0$0000fea9@sandos> <20030626151007.A877@grosbein.pp.ru> Date: Fri, 27 Jun 2003 03:16:04 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-stable@freebsd.org Subject: Re: Mbuf Clusters on 4.8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2003 01:15:59 -0000 > > From this it sounds as it is a problem that should be > > fixed, but it > > obviously isnt in 4.8. Is this behaviour now considered > > acceptable? And if > > so, doesnt this make FreeBSD extremely easy to kill > > using a simple > > DOS-attack? Is this "fixed" in any way on 5.1? > > Afaik, this bug was recently fixed in both of HEAD and STABLE. > > Eugene Yes, you could well be right. The fix about not checking return values from m_copy() when receiving broadcast messages I think, sure seems to fit what is happening to me. I disconnected my three machines from the rest of the LAN, and tried exhausting mbuf clusters again. This time, it didnt hang, and no rl0 watchdog messages either. I am ugprading the box now and will try a new kernel. --- John Bäckstrand