Hello Peter On 02/16/2016 11:30 PM, Peter Hurley wrote: > On 02/15/2016 07:28 AM, Michael Kerrisk (man-pages) wrote: >> Hello Tobias, >> >> On 02/15/2016 02:26 PM, Dr. Tobias Quathamer wrote: >>> See https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/tty/n_tty.c#n1673 >>> See https://bugs.debian.org/797479 >>> --- >>> man3/termios.3 | 9 +++++++++ >>> 1 file changed, 9 insertions(+) >>> >>> diff --git a/man3/termios.3 b/man3/termios.3 >>> index 7d738d4..3f57607 100644 >>> --- a/man3/termios.3 >>> +++ b/man3/termios.3 >>> @@ -728,11 +728,20 @@ requested fewer bytes than are available in the current line of input, >>> then only as many bytes as requested are read, >>> and the remaining characters will be available for a future >>> .BR read (2). >>> +.IP * 2 >>> +The maximum line length is 4096 chars (including the line termination >>> +char); lines longer than 4096 chars are truncated. After 4095 chars, >>> +input data is still processed but not stored. Overflow processing >>> +ensures the tty can always receive more input until at least one >>> +line can be read. >>> .PP >>> In noncanonical mode input is available immediately (without >>> the user having to type a line-delimiter character), >>> no input processing is performed, >>> and line editing is disabled. >>> +The read buffer will only accept 4095 chars; this provides the >>> +necessary space for a newline char if the input mode is switched >>> +to canonical. >>> The settings of MIN >>> .RI ( c_cc[VMIN] ) >>> and TIME >> >> Thanks for crafting this. I've applied, and tweaked a little to clarify >> some details: >> >> * The maximum line length is 4096 chars (including the terminating >> newline character); lines longer than 4096 chars are truncated. >> After 4095 characters, input data up (but not including) any ter‐ >> minating newline is discarded. This ensures that the terminal >> can always receive more input until at least one line can be >> read. > > Hmm. Neither description is accurate of the observable behavior from userspace. > For example, it's entirely possible to retrieve > 4096 bytes in non-canonical > mode, at least since 3.12 Note that the text I quoted applies just to canonical mode: In canonical mode: [...] * The maximum line length is 4096 chars (including the terminat‐ ing newline character); lines longer than 4096 chars are trun‐ cated. After 4095 characters, input data up (but not includ‐ ing) any terminating newline is discarded. This ensures that the terminal can always receive more input until at least one line can be read. So, does that seem okay? > And input processing continues on the input, even past 4096 bytes. > Line editing, ISIG, ECHOxx processing still occurs. Yes, but only in noncanonical mode, right? > > It is true that it is not possible to retrieve > 4096 char line in canonical > mode, and I don't see that ever changing via read() because userspace may > assume it has received a terminated line in 4096-byte read buffer. Yep. So we all seem to agree. > However, the noncanonical mode input buffer size may change in the near > future. Can you say some more about that? And what changed in 3.13 with respect to noncanonical mode, by the way? Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
