Messages in this thread | | | Date | Thu, 7 Oct 2004 02:16:34 +0100 (IST) | From | Paul Jakma <> | Subject | Re: UDP recvmsg blocks after select(), 2.6 bug? |
| |
On Wed, 6 Oct 2004, Richard B. Johnson wrote:
> thing --not. Select must return correct information.
It does, it's just state that select() reported on changed by the time user called recvmsg.
> When a function call like select() says there are data available, > there must be data available, period.
There was, but there wasnt when recvmsg() was called. Time changes things..
> If not, it's broken and needs to be fixed. Requiring one to set > sockets to non-blocking is a poor work- around for an otherwise > fatal flaw.
Any application that expects socket read not to block should set O_NONBLOCK.
> Cheers, > Dick Johnson
regards, -- Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A Fortune: Kansas state law requires pedestrians crossing the highways at night to wear tail lights. - 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/
| |