[lkml]   [2008]   [May]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [bug] stuck localhost TCP connections, v2.6.26-rc3+

* Ilpo Järvinen <> wrote:

> On Mon, 26 May 2008, Ingo Molnar wrote:
> > there's a hung distcc task on the system, waiting for socket action
> > forever:
> >
> > [root@europe ~]# strace -fp 19578
> > Process 19578 attached - interrupt to quit
> > select(5, NULL, [4], [4], {82, 90000} <unfinished ...>
> Hmm, readfds is NULL isn't it?!? Are you sure you straced the right
> process?

yes, i'm stracing the task that is hung unexpectedly.

> > disturbing that task via strace did not change the state of the
> > socket - and that's not unexpected as it's a select(). [TCP state
> > might be affected if strace impacted a recvmsg or a sendmsg wait
> > directly.]
> I fail to understand this paragraph due to excessive negation... :-)

i mean, sometimes a TCP connection can get 'unstuck' if you strace a
task - that is because the TCP related syscall the task sits in gets
interrupted. But in this case it's select() which doesnt explicitly take
the socket, doesnt do any tcp_push_pending_frames() processing, etc. -
it just its on the socket waitqueue AFAICS. And that's expected.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2008-05-26 18:27    [W:0.107 / U:3.504 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site