2008-06-02 06:20:33

by Herbert Xu

[permalink] [raw]
Subject: Re: [bug] stuck localhost TCP connections, v2.6.26-rc3+

Ilpo J??rvinen <[email protected]> wrote:
>
> Before:
> tcp 65436 0 lo:5000 lo:59980 ESTABLISHED -

This is what happens before accept(2) is called. Ingo, please
strace the process that owns the listening socket to make sure
that it is actually calling accept(2). If it ever stops calling
accept(2) then this is expected behaviour.

Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt


2008-06-02 11:53:28

by Ilpo Järvinen

[permalink] [raw]
Subject: Re: [bug] stuck localhost TCP connections, v2.6.26-rc3+

On Mon, 2 Jun 2008, Herbert Xu wrote:

> Ilpo J??rvinen <[email protected]> wrote:
> >
> > Before:
> > tcp 65436 0 lo:5000 lo:59980 ESTABLISHED -
>
> This is what happens before accept(2) is called. Ingo, please
> strace the process that owns the listening socket to make sure
> that it is actually calling accept(2). If it ever stops calling
> accept(2) then this is expected behaviour.

Shouldn't that be already visible in the ingo's sysrq-t dump, no? There:

http://marc.info/?l=linux-kernel&m=121182099131520&w=2

There are many sys_accepts at least (if I understand that dump at all).
There were some ip_local_outs there as well, which made me wonder if the
totally innocent looking commit 1ac06e0306d0192a7a4d9ea1c9e06d355ce7e7d3
(ipsec: Use the correct ip_local_out function) has something to do with
this (I definately don't understand that part at all).

--
i.

2008-06-02 14:09:22

by Herbert Xu

[permalink] [raw]
Subject: Re: [bug] stuck localhost TCP connections, v2.6.26-rc3+

On Mon, Jun 02, 2008 at 02:53:09PM +0300, Ilpo J?rvinen wrote:
>
> Shouldn't that be already visible in the ingo's sysrq-t dump, no? There:
>
> http://marc.info/?l=linux-kernel&m=121182099131520&w=2

No, we need an actual strace rather than the static stack back-trace.
So start with netstat -lntp to locate the process listening on that
port, and then strace it to see if it's calling accept.

> There are many sys_accepts at least (if I understand that dump at all).
> There were some ip_local_outs there as well, which made me wonder if the
> totally innocent looking commit 1ac06e0306d0192a7a4d9ea1c9e06d355ce7e7d3
> (ipsec: Use the correct ip_local_out function) has something to do with
> this (I definately don't understand that part at all).

This patch only has an effect for IPsec.

Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt