[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091119.154038.194307613.davem@davemloft.net>
Date: Thu, 19 Nov 2009 15:40:38 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: ilpo.jarvinen@...sinki.fi
Cc: jarkao2@...il.com, holger.hoffstaette@...glemail.com,
netdev@...r.kernel.org, eric.dumazet@...il.com, zbr@...emap.net
Subject: Re: Network hangs with 2.6.30.5
From: "Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
Date: Fri, 2 Oct 2009 11:11:55 +0300 (EEST)
> On Thu, 1 Oct 2009, David Miller wrote:
>
>> From: Jarek Poplawski <jarkao2@...il.com>
>> Date: Mon, 7 Sep 2009 07:21:43 +0000
>>
>> I also looked through all the TCP commits in 2.6.29 to 2.6.30
>> and I could not find anything else that might cause stalls with
>> time-wait recycled connections.
>
> What about the more than 64k connections change a9d8f9110d7e953c2f2 (or
> its fixes), it might be another possibility? ...It certainly does
> something related to reuse and happens to be in the correct time frame...
> (I've added Evgeniy).
So I've been studying this one quite a bit.
This change could only cause problems in timewait recycling if it:
1) Would accept using a bind bucket that previously it would not
2) Caused socket corruption due to bad locking
And I can find neither problem with the Evgeniy's bind changes.
So we've back to square one I think.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists