Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763478AbYFEX3n (ORCPT ); Thu, 5 Jun 2008 19:29:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753327AbYFEX33 (ORCPT ); Thu, 5 Jun 2008 19:29:29 -0400 Received: from linode.ducksong.com ([64.22.125.164]:56784 "EHLO linode.ducksong.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753268AbYFEX32 (ORCPT ); Thu, 5 Jun 2008 19:29:28 -0400 Subject: Re: [fixed] [patch] Re: [bug] stuck localhost TCP connections, v2.6.26-rc3+ From: Patrick McManus To: Ilpo =?ISO-8859-1?Q?J=E4rvinen?= Cc: Ingo Molnar , David Miller , peterz@infradead.org, LKML , Netdev , rjw@sisk.pl, Andrew Morton , johnpol@2ka.mipt.ru In-Reply-To: References: <20080603094057.GA29480@elte.hu> <20080603.150344.145518113.davem@davemloft.net> <20080605142244.GA19216@elte.hu> Content-Type: text/plain; charset=ISO-8859-1 Date: Thu, 05 Jun 2008 19:29:31 -0400 Message-Id: <1212708571.19522.10.camel@tng> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1.1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1358 Lines: 34 On Fri, 2008-06-06 at 00:13 +0300, Ilpo J?rvinen wrote: > > I'm out of new ideas what could be still wrong (I got confused and > lost > track number of times while I tried to verify socket locking today and > probably don't have more time for that now)... Unless somebody else > (Patrick?) comes up with something quickly, Sorry, I don't see anything - it seems to boil down to the same code in the DA and non-DA case as far as I can tell, but after a while all the twisty passages seem to look alike. If Ingo confirms that the recv end was running the locking patch code, it would be interesting to just confirm the sysreq+t looks the same as before - it is possible the patch turned the race into a non-obvious deadlock. I'm sure your smaller revert will make the problem go away just as the larger one did, fwiw. The other odd thing is that Ingo did a lot of experimentation and was only making this happen on localhost before (though I agree there is nothing inherent about that lock and localhost) - isn't it odd that the first trigger of it now is between two hosts? What do you make of that? -- 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/