diff options
author | Gabriel Krisman Bertazi <krisman@collabora.com> | 2020-08-19 23:07:31 +0300 |
---|---|---|
committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2020-09-09 06:31:33 +0300 |
commit | 20d0a107fb35f37578b919f62bd474d6d358d579 (patch) | |
tree | 905c81ff334da88e122430b27bc3e554612c6637 /.mailmap | |
parent | e2cab031ba7b5003cd12185b3ef38f1a75e3dae8 (diff) | |
download | linux-20d0a107fb35f37578b919f62bd474d6d358d579.tar.xz |
f2fs: Return EOF on unaligned end of file DIO read
Reading past end of file returns EOF for aligned reads but -EINVAL for
unaligned reads on f2fs. While documentation is not strict about this
corner case, most filesystem returns EOF on this case, like iomap
filesystems. This patch consolidates the behavior for f2fs, by making
it return EOF(0).
it can be verified by a read loop on a file that does a partial read
before EOF (A file that doesn't end at an aligned address). The
following code fails on an unaligned file on f2fs, but not on
btrfs, ext4, and xfs.
while (done < total) {
ssize_t delta = pread(fd, buf + done, total - done, off + done);
if (!delta)
break;
...
}
It is arguable whether filesystems should actually return EOF or
-EINVAL, but since iomap filesystems support it, and so does the
original DIO code, it seems reasonable to consolidate on that.
Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions