From owner-freebsd-net@FreeBSD.ORG Mon Nov 5 11:35:29 2012 Return-Path: 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 A46F0C9E for ; Mon, 5 Nov 2012 11:35:29 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 01A048FC15 for ; Mon, 5 Nov 2012 11:35:28 +0000 (UTC) Received: (qmail 80774 invoked from network); 5 Nov 2012 13:11:07 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 5 Nov 2012 13:11:07 -0000 Message-ID: <5097A47D.1060005@freebsd.org> Date: Mon, 05 Nov 2012 12:35:25 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Fabian Keil Subject: Re: kern/173309: [tcp] TCP connections often prematurely closed by the server side after r242262 [regression] References: <201211032251.qA3Mpnp6017076@freefall.freebsd.org> <5095B953.9060301@freebsd.org> <20121104132957.3965dc99@fabiankeil.de> <5096C6CA.4090306@freebsd.org> <20121104225226.500507a3@fabiankeil.de> <5096E8FD.6040103@freebsd.org> <20121105002509.670ca1fc@fabiankeil.de> <50978469.8000001@freebsd.org> <20121105110928.480a68b3@fabiankeil.de> In-Reply-To: <20121105110928.480a68b3@fabiankeil.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 11:35:29 -0000 On 05.11.2012 11:09, Fabian Keil wrote: > Andre Oppermann wrote: > >> I've backed out the change with r242601 as it exhibits still too >> many problems. I'll fix these problems in the next days but in >> the mean time HEAD should be in a working state. >> >> I'll be grateful if I could send you the fixed change for testing >> before it goes into HEAD again. > > Sure. Thanks. Can you please confirm that HEAD after the backout is behaving as it should again? -- Andre