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  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]
Date:	Sat, 31 May 2008 08:09:47 +0200
From:	Ingo Molnar <>
To:	Ilpo J?rvinen <>
Cc:	LKML <>,
	Netdev <>,
	"David S. Miller" <>,
	"Rafael J. Wysocki" <>,
	Andrew Morton <>
Subject: Re: [bug] stuck localhost TCP connections, v2.6.26-rc3+

* Ingo Molnar <> wrote:

> ah, in retrospect i realized that this test had one flaw: some of the 
> systems i the build cluster already ran a newer kernel and hence were 
> targets for this bug.
> so i turned off CONFIG_TCP_CONG_CUBIC on all the testboxes and 
> rebooted the cluster boxes into 2.6.25, and the hung sockets are now 
> gone. (about 150 successful iterations)
> i did another change as well: i removed the localhost distcc 
> component. I'll reinstate that now to make sure it's really related to 
> TCP_CONG_CUBIC and not to localhost networking.

ok, once i added back the localhost distcc component and the hung kernel 
build + stuck TCP socket bug happened again overnight:

 Active Internet connections (w/o servers)
 Proto Recv-Q Send-Q Local Address               Foreign Address             State
 tcp    72187      0                 ESTABLISHED
 tcp        0 174464                 ESTABLISHED

so it seems distcc over localhost was the aspect that made it fail.

_Perhaps_ what matters is to have the new post-rc3 TCP code on _both_ 
sides of the connection. But that is just a theory - it could be timing, 

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists