From owner-freebsd-current Thu Sep 10 08:21:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14305 for freebsd-current-outgoing; Thu, 10 Sep 1998 08:21:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ducky.net (gate.ducky.net [198.145.101.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14231 for ; Thu, 10 Sep 1998 08:21:11 -0700 (PDT) (envelope-from mike@ducky.net) Received: from ducky.net (localhost.ducky.net [127.0.0.1]) by ducky.net (8.9.1/8.8.5) with ESMTP id IAA00322; Thu, 10 Sep 1998 08:20:05 -0700 (PDT) Message-Id: <199809101520.IAA00322@ducky.net> To: Doug Rabson cc: Mike Haertel , current@FreeBSD.ORG, wollman@khavrinen.lcs.mit.edu, mike@ducky.net Subject: Re: DANGER: new IP fragment code breaks SLIP In-reply-to: Your message of "Thu, 10 Sep 1998 10:38:28 BST." Date: Thu, 10 Sep 1998 08:20:05 -0700 From: Mike Haertel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >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! Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message