From owner-freebsd-net@FreeBSD.ORG  Thu Jul 12 04:01:23 2007
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: net@freebsd.org
Delivered-To: freebsd-net@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 1317816A400;
	Thu, 12 Jul 2007 04:01:23 +0000 (UTC)
	(envelope-from rea-fbsd@codelabs.ru)
Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45])
	by mx1.freebsd.org (Postfix) with ESMTP id B3CB313C44C;
	Thu, 12 Jul 2007 04:01:22 +0000 (UTC)
	(envelope-from rea-fbsd@codelabs.ru)
DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru;
	h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject;
	b=NFQraD/xZ20H3b8HoXlrxZXWQ+1LkdQXJV0Kww7AbGb+ngbkxGtsCo+eLTJUGoW9eifJwz3wufgMzvxpiKFge8aND+Tc5D6l53dQlKSLrg78NsdaVb5q5MQUVnOcMcT7eyPMeXCe14goiXETj49cIHC/oKFAnGq7ps/Y5/m8bqM=;
Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25])
	by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256)
	id 1I8prk-0007wB-He; Thu, 12 Jul 2007 08:01:20 +0400
Date: Thu, 12 Jul 2007 08:01:15 +0400
From: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
To: Mike Silbersack <silby@silby.com>
Message-ID: <20070712040115.GK1038@void.codelabs.ru>
References: <20070709234401.S29353@odysseus.silby.com>
	<20070710132253.GJ1038@void.codelabs.ru>
	<20070710202028.I34890@odysseus.silby.com>
	<20070711060423.GV1038@void.codelabs.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <20070711060423.GV1038@void.codelabs.ru>
Sender: rea-fbsd@codelabs.ru
X-Spam-Status: No, score=-3.0 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_00
Cc: Robert Watson <rwatson@freebsd.org>, Andre Oppermann <andre@freebsd.org>,
	current@freebsd.org, net@freebsd.org
Subject: Re: FreeBSD 7 TCP syncache fix: request for testers
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2007 04:01:23 -0000

Good day.

Wed, Jul 11, 2007 at 10:04:23AM +0400, Eygene Ryabinkin wrote:
> OK, maybe I have something that can be related to this bug.  It
> provokes another message, 'Spurious RST', but can be correlated
> with your guess.  What is happening is that when one side closes
> the connection and releases the socket (running -CURRENT) while the
> other one is still pushing data through the connection, we are
> getting 'Spurious RST' messages.  This happens, because we are
> checking the 'so->so_state' for the presence of the 'SS_NOFDREF'
> flag (tcp_input.c, version 1.361, line 1581) and dropping such
> connections with RST.  But the connection was already closed (living
> in the FIN-WAIT-2 state, to be precise) from that side, so it
> provokes the debug message.

To clarify one point: the first RST is due to the SS_NOFDREF flag.
The rest of RSTs are spitted out because the corresponding connection
was closed by tcp_close() just before the first RST.
-- 
Eygene