readv/writev: do the same MAX_RW_COUNT truncation that read/write does
authorLinus Torvalds <torvalds@linux-foundation.org>
Fri, 29 Oct 2010 17:36:49 +0000 (10:36 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Fri, 29 Oct 2010 17:36:49 +0000 (10:36 -0700)
commit435f49a518c78eec8e2edbbadd912737246cbe20
tree106df2617d42ace231e2fa9fcf1e0fd1075874ea
parentf56f44001cb5b40089deac094dbb74e5c9f64d81
readv/writev: do the same MAX_RW_COUNT truncation that read/write does

We used to protect against overflow, but rather than return an error, do
what read/write does, namely to limit the total size to MAX_RW_COUNT.
This is not only more consistent, but it also means that any broken
low-level read/write routine that still keeps counts in 'int' can't
break.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
fs/compat.c
fs/read_write.c
include/linux/fs.h