diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2021-01-21 10:17:25 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2021-01-21 10:34:33 -0800 |
commit | 2b3da8cf7ecafe48704f62046fce5da5d17b9e6a (patch) | |
tree | 005cbf23d91c903a62de3de7a75b0e10a261bcae /scripts/gcc-x86_64-has-stack-protector.sh | |
parent | 1443b92a1ff3a0af5f0e5a177db2d843273a2ca1 (diff) | |
download | linux-tty-splice.tar.gz linux-tty-splice.tar.bz2 linux-tty-splice.zip |
tty: fix up iterate_tty_read() EOVERFLOW handlingtty-splice
When I converted the tty_ldisc_ops 'read()' function to take a kernel
pointer, I was a bit too aggressive about the ldisc returning EOVERFLOW.
Yes, we want to have EOVERFLOW override any partially read data (because
the whole point is that the buffer was too small for the whole packet,
and we don't want to see partial packets), but it shouldn't override a
previous EFAULT.
And in fact, it really is just EOVERFLOW that is special and should
throw away any partially read data, not "any error". Admittedly
EOVERFLOW is currently the only one that can happen for a continuation
read - and if the first read iteration returns an error we won't have this issue.
So this is more of a technicality, but let's just make the intent very
explicit, and re-organize the error handling a bit so that this is all
clearer.
Reported-by: Jiri Slaby <jirislaby@kernel.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'scripts/gcc-x86_64-has-stack-protector.sh')
0 files changed, 0 insertions, 0 deletions