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:	Wed, 4 Jun 2008 16:00:29 +0200
From:	"Håkon Løvdal" <hlovdal@...il.com>
To:	"Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Netdev <netdev@...r.kernel.org>, "Ingo Molnar" <mingo@...e.hu>,
	"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+

2008/6/4 Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>:
> On Wed, 4 Jun 2008, Håkon Løvdal wrote:
>
>> Hi. I have now tested and taken various logs before/under/after (ps,
>> netstat, tcpdump, strace, /proc/net/tcp). The logs did not grow as big
>> as I feared however they are way too big attach here. Any tips on how to
>> distribute?
>
> Usually such logs compress quite well. A best thing might be to put
> somewhere (if possible) and http:// reference them.

The largest file was a strace log of 1.5GB uncompressed. I will try to
sort out something.


>> //netstat before the hang:
>> Proto Recv-Q Send-Q Local Address               Foreign Address
>>      State       PID/Program name    Timer
>> tcp        0    504 new_pc:22                   old_pc:39464
>>      ESTABLISHED 17054/sshd: hlovdal on (0.20/0/0)
>>
>> // after the hang:
>> Proto Recv-Q Send-Q Local Address               Foreign Address
>>      State       PID/Program name    Timer
>> tcp        0   2896 old_pc:22                   new_pc:39464
>>      ESTABLISHED -                   on (21329441.19/0/0)
>
> ??? Are these on the same machine? How come the ip-addresses got reversed
> (while ports remain the same)...?!?

Oops, that was an editing mistake on my part, old and new are mixed up
in the last line.

BR Håkon Løvdal