Hi Michael, Some issues have arisen [1] regarding a discrepancy between the Linux behavior of read() on a tty and 'man termios' and 'Linux Programming Interface', Chapter 62.
Firstly, if MIN==0 and TIME==0 and no input is available, read() returns 0, even if O_NONBLOCK is set. This is also true of the other non-canonical read()'s with timeout (TIME > 0). 'man termios' is silent here, but 62.6.2 in LPI implies that O_NONBLOCK will return -1 with errno==EAGAIN; it does not. This is unspecified by POSIX (11.1.7). Secondly, in all 4 of the non-canonical read() modes, the MIN value does not limit the number of bytes which may be returned by the read(). Only the 'count' parameter to read() has this effect. LPI has this to say (man-pages reads similar): "MIN > 0, TIME == 0 (blocking read) The read() blocks (possibly indefinitely) until the lesser of the number of bytes requested or MIN bytes are available, and returns the lesser of the two values." However, read() may unblock when MIN bytes are available but return up to the 'count' parameter if more input arrives in between waking and copying into the user buffer. So, for example, if MIN == 5, n = read(tty, &buffer, 30 /*sizeof(buffer)*/) n may be up to 30 on return. Finally, if the 'count' parameter is less than MIN, read() may return before MIN bytes have been received, if 'count' bytes have been received. Regards, Peter Hurley [1] https://bugzilla.kernel.org/show_bug.cgi?id=71671 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
