linux-kernel - Re: bug in select() in linux

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] [day] [month] [year] [list]

Date:	Mon, 12 Mar 2007 17:03:02 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Lluís Batlle" <viriketo@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: bug in select() in linux

On Mon, 12 Mar 2007 16:02:11 +0100
"Lluís Batlle" <viriketo@...il.com> wrote:

> 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.

You can because the only case it will block is when the transmit queue is
partly or completely full which means that you will discover the
connection has been reset when the transmit triggers a reset.

If you wait on the FD concerned for write or exception events all should
work nicely.
-
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/