[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0806040104340.3474@wrl-59.cs.helsinki.fi>
Date: Wed, 4 Jun 2008 01:10:03 +0300 (EEST)
From: "Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To: David Miller <davem@...emloft.net>
cc: mingo@...e.hu, peterz@...radead.org,
LKML <linux-kernel@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>, rjw@...k.pl,
Andrew Morton <akpm@...ux-foundation.org>, johnpol@....mipt.ru,
mcmanus@...ksong.com
Subject: Re: [fixed] [patch] Re: [bug] stuck localhost TCP connections,
v2.6.26-rc3+
On Tue, 3 Jun 2008, David Miller wrote:
> From: "Ilpo_Järvinen" <ilpo.jarvinen@...sinki.fi>
> Date: Wed, 4 Jun 2008 01:01:25 +0300 (EEST)
>
> > 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.
>
> Keepalive is very long, it might still "seem" like a deadlock for
> someone without much patience :-)
Sure, but I think Ingo kept it once hang for hours, ~8h or so...
...Though I'm not sure if that qualifies as a proof of Ingo's patience
but rather shows his willingness to help solving the matter... ;-)
--
i.
Powered by blists - more mailing lists