netdev - Re: Network hangs with 2.6.30.5

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.DEB.2.00.0911201406210.7024@wel-95.cs.helsinki.fi>
Date:	Fri, 20 Nov 2009 14:09:35 +0200 (EET)
From:	"Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To:	Evgeniy Polyakov <zbr@...emap.net>
cc:	David Miller <davem@...emloft.net>, jarkao2@...il.com,
	holger.hoffstaette@...glemail.com, Netdev <netdev@...r.kernel.org>,
	eric.dumazet@...il.com
Subject: Re: Network hangs with 2.6.30.5

On Fri, 20 Nov 2009, Evgeniy Polyakov wrote:

> On Thu, Nov 19, 2009 at 03:40:38PM -0800, David Miller (davem@...emloft.net) wrote:
> > >> 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.
> 
> Wasn't solution found for this problem, I recall related discussion
> recently, or should I dig deeper into this one?

Nothing that I know off (but that's not too reassuring I'd say). IIRC, 
there were two independent problems same looking problems and one of them 
turned out to be related to something else while the other problem 
withstands but that guy's hw broke so the test case will no longer be 
available or something like that.

-- 
 i.
--
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