From owner-freebsd-current  Sat Nov  2 15:10:49 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2991037B401
	for <current@freebsd.org>; Sat,  2 Nov 2002 15:10:48 -0800 (PST)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A019243E91
	for <current@freebsd.org>; Sat,  2 Nov 2002 15:10:47 -0800 (PST)
	(envelope-from fenner@research.att.com)
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 8F6684CFCC; Sat,  2 Nov 2002 18:10:46 -0500 (EST)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id SAA24834;
	Sat, 2 Nov 2002 18:10:46 -0500 (EST)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost)
	by windsor.research.att.com (8.8.8+Sun/8.8.5) id PAA21596;
	Sat, 2 Nov 2002 15:10:46 -0800 (PST)
Message-Id: <200211022310.PAA21596@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: tlambert2@mindspring.com
Subject: Re: crash with network load (in tcp syncache ?)
Cc: current@freebsd.org
References:  <Pine.BSF.4.41.0211020937210.87031-100000@prg.traveller.cz> <3DC3B701.58AA03ED@mindspring.com> <200211021742.JAA18603@windsor.research.att.com> <3DC44B72.5C7C3C5E@mindspring.com>
Date: Sat, 2 Nov 2002 15:10:45 -0800
Versions: dmail (solaris) 2.5a/makemail 2.9d
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


I really don't understand why you keep claiming that the SYN cache
changes anything.  Without the SYN cache, tcp_input() calls
sonewconn(so, 0) on receipt of a SYN; with the SYN cache, tcp_input()
calls some syncache function which calls sonewconn(so, SS_ISCONNECTED)
on receipt of a SYN/ACK.  In either case, it's with the same interrupt
level, etc -- you are in the middle of processing a packet that was
received by tcp_input().

So, you're saying that what we're hitting is a design flaw in 4BSD
and that this problem has been there since day one?

  Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message