lkml.org 
[lkml]   [2007]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: bug in select() in linux
Oh, of course you're right. I was inside too much layers to think of
the tcp protocol, and I did not pay attention to it.

Maybe something could be added to the manpage anyway.

The bad thing is that there's no way I can use a socket for writing
using select() if that connection has been half-closed by the other
end. Moo.

Thanks a lot for your time,
Lluís

2007/3/12, Alan Cox <alan@lxorguk.ukuu.org.uk>:
> > I've tried a select() for write against a closed tcp socket (closed by
> > the other side), and the select call _blocks_.
>
> A TCP close from the remote node is single sided. It sends a FIN and we
> ACK the FIN, that means only that the remote node has completed *sending*.
>
> > Any write() call to that socket will _not block_, and will return with EPIPE.
>
> We don't know this until you try the write. At that point the other end
> if it has closed entirely will issue an RST and terminate the connection
> in full.
>
> I don't therefore believe that this is actually a bug.
>
> Alan
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-03-12 16:05    [W:0.020 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site