linux-kernel - Re: [fixed] [patch] Re: [bug] stuck localhost TCP connections, v2.6.26-rc3+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0806042202030.6328@wrl-59.cs.helsinki.fi>
Date:	Wed, 4 Jun 2008 23:56:34 +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 Wed, 4 Jun 2008, David Miller wrote:

> From: Ingo Molnar <mingo@...e.hu>
> Date: Wed, 4 Jun 2008 09:23:11 +0200
> 
> > * Ilpo Järvinen <ilpo.jarvinen@...sinki.fi> 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...
> > 
> > i'll queue it up for testing, but no promises about speedy action here - 
> > the test cycle is really long with this bug.
> 
> Ilpo posted another patch which fixes a locking bug in the
> code, please test with that patch.  I include it below so
> that you know exactly which one I am referring to.

Do you know if TCP ever needs to lock the child sk again (after creating 
it and it has started to live on its own) from a context that has already 
locked the listen_sk (it could deadlock after this change)?


-- 
 i.