Messages in this thread | | | From | "Hua Zhong" <> | Subject | RE: UDP recvmsg blocks after select(), 2.6 bug? | Date | Wed, 6 Oct 2004 12:43:27 -0700 |
| |
> It may need fixing in the sense that it must point out that > the Linux kernel > might not conform to POSIX in its handling of select on sockets.
Agreed.
> We now not only have "man 2 select", but also "man 3p select". > This is the POSIX text: > > A descriptor shall be considered ready for reading when a > call to an input function with O_NONBLOCK clear would not > block, whether or not the function would transfer data > successfully. (The function might return data, an end-of- > file indication, or an error other than one indicating > that it is blocked, and in each of these cases the > descriptor shall be considered ready for reading.) > > As far as I can interpret these sentences, Linux does not conform.
How hard is it to treat the next read to the fd as NON_BLOCKING, even if it's not set?
> Andries
- 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/
| |