diff options
author | Christoph Hellwig <hch@lst.de> | 2020-09-03 16:22:33 +0200 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2020-09-08 22:21:31 -0400 |
commit | 4d03e3cc59828c82ee89ea6e27a2f3cdf95aaadf (patch) | |
tree | 47b12f217a59842f4b5e25bca6b4ab038b10dbc0 /fs/splice.c | |
parent | 4bd6a7353ee14697fea645e941354976d2c4a452 (diff) |
fs: don't allow kernel reads and writes without iter ops
Don't allow calling ->read or ->write with set_fs as a preparation for
killing off set_fs. All the instances that we use kernel_read/write on
are using the iter ops already.
If a file has both the regular ->read/->write methods and the iter
variants those could have different semantics for messed up enough
drivers. Also fails the kernel access to them in that case.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/splice.c')
0 files changed, 0 insertions, 0 deletions