From owner-freebsd-current Thu Sep 10 16:33:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26750 for freebsd-current-outgoing; Thu, 10 Sep 1998 16:33:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26732 for ; Thu, 10 Sep 1998 16:33:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id AAA23240; Fri, 11 Sep 1998 00:34:12 +0100 (BST) Date: Fri, 11 Sep 1998 00:34:12 +0100 (BST) From: Doug Rabson To: Mike Haertel cc: current@FreeBSD.ORG, wollman@khavrinen.lcs.mit.edu Subject: Re: DANGER: new IP fragment code breaks SLIP In-Reply-To: <199809101520.IAA00322@ducky.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 10 Sep 1998, Mike Haertel wrote: > >On Sat, 5 Sep 1998, Mike Haertel wrote: > > > >> I've been experiencing crashes with recent 3.0 kernels using SLIP > >> based dialin networking. Haven't had time yet to set up kernel > >> debugging, however I spent a half an hour doing binary search via > >> kernel builds on recent CVS commits. The bug is either contained > >> in, or perhaps exposed by, the following commit: > > > >I believe that I have fixed your problem. Could you update ip_input.c and > >re-test, thanks. > > Just tried it, it appears to work. Sorry I didn't get a chance > to get your m_nextpkt panic code in; I was going to have done > that tonight, but you beat me to it. > > Thanks! You are welcome :-) -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message