readv/writev: do the same MAX_RW_COUNT truncation that read/write does

Browse source

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>

...

This commit is contained in:

Linus Torvalds 2010-10-29 10:36:49 -07:00

parent f56f44001c

commit 435f49a518

3 changed files with 40 additions and 35 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

12

fs/compat.c

View file

62

fs/read_write.c

View file

1

include/linux/fs.h

View file