Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261998AbTFDAMo (ORCPT ); Tue, 3 Jun 2003 20:12:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262000AbTFDAMo (ORCPT ); Tue, 3 Jun 2003 20:12:44 -0400 Received: from blackbird.intercode.com.au ([203.32.101.10]:50447 "EHLO blackbird.intercode.com.au") by vger.kernel.org with ESMTP id S261998AbTFDAM1 (ORCPT ); Tue, 3 Jun 2003 20:12:27 -0400 Date: Wed, 4 Jun 2003 10:24:14 +1000 (EST) From: James Morris To: davidm@hpl.hp.com cc: Martin Josefsson , , , , , "David S. Miller" Subject: Re: fix TCP roundtrip time update code In-Reply-To: <16092.60612.352739.581639@napali.hpl.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1150 Lines: 32 On Tue, 3 Jun 2003, David Mosberger wrote: > Martin> I tested this patch and it looks like it has cured my > Martin> mysterious TCP stalls. > > Yes, this sounds reasonable. I wasn't very clear on this point, but > "by going south" I meant that TCP is starting to misbehave. In > particular, you'll likely end up with the kernel aborting ESTABLISHED > TCP connections with extreme prejudice (and in violation of the TCP > protocol), because it thought that it had been unable to communicate > with the remote end for a _very_ long time. The net effect typically > is that you end up with one end having a connection that's in the > ESTABLISHED state and the other end having no trace of that > connection. David, This might be the solution to one of the 'must-fix' bugs for the networking, which nobody so far was quite able to track down. - James -- James Morris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/