Date: Thu, 20 Nov 1997 19:50:01 -0800 (PST) From: Bill Fenner <fenner@parc.xerox.com> To: freebsd-bugs Subject: Re: kern/5103: FreeBSD kernel lockup from spoofed TCP packet Message-ID: <199711210350.TAA08131@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/5103; it has been noted by GNATS. From: Bill Fenner <fenner@parc.xerox.com> To: freebsd-gnats-submit@hub.freebsd.org Cc: Subject: Re: kern/5103: FreeBSD kernel lockup from spoofed TCP packet Date: Thu, 20 Nov 1997 19:40:35 PST Garrett Wollman <wollman@khavrinen.lcs.mit.edu> wrote: > There is still an underlying bug, since > self-connect not only should work, but once did. Since 2.2.2 was OK, and 2.2.5 wasn't, it was pretty easy to determine that it's the part of 1.52 that was removed in 1.63 and 1.54.2.5 that causes 2.2.2 to be OK. It's clear that we don't want to just re-revert 1.63/1.54.2.5, since it caused other problems. One path to go down to understand exactly what's going on might be to build with TCPDEBUG and send one of these nastygrams to a server that has SO_DEBUG set. You'd need a serial console, since constantly printing messages seems to eliminate your ability to use the scrollback (at least, hitting scroll lock to pause the messages flying by didn't do anything other than make it start beeping after a few seconds). I don't have a convenient serial console, unfortunately, or I'd pursue this. Bill
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711210350.TAA08131>