Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758938AbYFCWBl (ORCPT ); Tue, 3 Jun 2008 18:01:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753247AbYFCWB1 (ORCPT ); Tue, 3 Jun 2008 18:01:27 -0400 Received: from courier.cs.helsinki.fi ([128.214.9.1]:44885 "EHLO mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752997AbYFCWB0 (ORCPT ); Tue, 3 Jun 2008 18:01:26 -0400 Date: Wed, 4 Jun 2008 01:01:25 +0300 (EEST) From: "=?ISO-8859-1?Q?Ilpo_J=E4rvinen?=" X-X-Sender: ijjarvin@wrl-59.cs.helsinki.fi To: Ingo Molnar cc: Peter Zijlstra , LKML , Netdev , "David S. Miller" , "Rafael J. Wysocki" , Andrew Morton , Evgeniy Polyakov , Patrick McManus Subject: Re: [fixed] [patch] Re: [bug] stuck localhost TCP connections, v2.6.26-rc3+ In-Reply-To: Message-ID: References: <20080529084524.GA24892@elte.hu> <20080529112257.GA18130@elte.hu> <20080530181839.GA31915@elte.hu> <20080531060947.GA26441@elte.hu> <20080531125428.GA22111@elte.hu> <20080531163501.GB22607@elte.hu> <20080603094057.GA29480@elte.hu> MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; boundary="-696208474-742855239-1212522473=:3474" Content-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1274 Lines: 32 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---696208474-742855239-1212522473=:3474 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Content-ID: On Wed, 4 Jun 2008, Ilpo J?rvinen wrote: > ...I couldn't immediately find anything obviously wrong with those changes > but the patch below might be worth of a try (without the revert of > course). If it ever spits out that WARN_ON for you, we were playing with > fire too much and it's better to return on the safe side there... > [PATCH] tcp DEFER_ACCEPT: see if header prediction got turned on > > If header prediction is turned on under some circumstances, > DA can deadlock though I have great trouble in figuring out ...Nah, keepalive timer would then eventually kill it then, so no deadlock seems possible through that one. -- i. ---696208474-742855239-1212522473=:3474-- -- 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/