linux-kernel - 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]

Date:	Fri, 30 May 2008 13:09:04 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Ilpo J?rvinen <ilpo.jarvinen@...sinki.fi>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Netdev <netdev@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [bug] stuck localhost TCP connections, v2.6.26-rc3+

* Ingo Molnar <mingo@...e.hu> wrote:

> btw., i now also have a hung socket over real network:

last night i turned off distcc support, and got about 200 successful 
bootups and zero TCP hangs (as expected - there's not much TCP traffic 
if the distcc cluster is not utilized).

but that's 200 overnight tests instead of the expected 600, so this is a 
major and rather crippling bug to me.

There's no good way to detect these hung sockets by me from userspace 
and get rid of them. Has anyone before thought of the obvious: to write 
a kernel-space "TCP socket watchdog" kernel feature that detects them 
and tries to free them so that people can become aware of it?

Hung sockets is a re-occuring bug in the TCP stack after all. (and it's 
a natural property of it: state machine designs are always vulnerable to 
lost event problems.)

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/