summaryrefslogtreecommitdiff
path: root/fs/read_write.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-04-01 19:35:56 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2022-04-01 19:35:56 -0700
commita4251ab9896cefd75926b11c45aa477f8464cdec (patch)
tree64da1d49438ba5668d2432911fb7b7b1e3a48482 /fs/read_write.c
parentb32e3819a8230332d7848a6fb067aee52d08557e (diff)
parent49df34221804cfd6384135b28b03c9461a31d024 (diff)
Merge tag 'vfs-5.18-merge-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
Pull vfs fix from Darrick Wong: "The erofs developers felt that FIEMAP should handle ranged requests starting at s_maxbytes by returning EFBIG instead of passing the filesystem implementation a nonsense 0-byte request. Not sure why they keep tagging this 'iomap', but the VFS shouldn't be asking for information about ranges of a file that the filesystem already declared that it does not support. - Fix a potential infinite loop in FIEMAP by fixing an off by one error when comparing the requested range against s_maxbytes" * tag 'vfs-5.18-merge-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux: fs: fix an infinite loop in iomap_fiemap
Diffstat (limited to 'fs/read_write.c')
0 files changed, 0 insertions, 0 deletions