From owner-freebsd-security Wed May 19 16:24:54 1999 Delivered-To: freebsd-security@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id 8569C157D2 for ; Wed, 19 May 1999 16:24:50 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id RAA19752; Wed, 19 May 1999 17:24:43 -0600 (MDT) Message-Id: <4.2.0.37.19990519171457.045fc350@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.37 (Beta) Date: Wed, 19 May 1999 17:17:20 -0600 To: Warner Losh From: Brett Glass Subject: Re: Is 3.2-R safe? Cc: security@FreeBSD.ORG In-Reply-To: <199905192038.OAA01429@harmony.village.org> References: <4.2.0.37.19990518110133.00b58da0@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In that case, it probably still needs fixing. What concerns me is that this error may be triggered by other things besides just SYN floods. Any heavy load might do it. And then, you'll get kernel panics. Not good. I'd like to do the patch, but I'm not up on the mysteries of that particular part of the kernel -- and the source isn't exactly well commented. Who is the person who has most recently tinkered with that code? --Brett Glass >I don't recall a "fix" for this going into -current, let alone >-stable. It all came to light very late in the 3.2 game, and no body >posted a good patch, as far as I can recall. The one patch that was >posted was panned as being bad. I had planned on setting up a 3.2R >system to see if this, and a small list of other problems, has been >fixed or not. > >Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message