]> git.baikalelectronics.ru Git - kernel.git/commit
Merge tag 'vfs-5.18-merge-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
authorLinus Torvalds <torvalds@linux-foundation.org>
Sat, 2 Apr 2022 02:35:56 +0000 (19:35 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Sat, 2 Apr 2022 02:35:56 +0000 (19:35 -0700)
commit8e91eb1b8a633be440be5e0e7cef0e950da6a04d
tree64da1d49438ba5668d2432911fb7b7b1e3a48482
parentc56303787f4b9716c61a1ee5c135b182591a3537
parent6cbfa0d5eaa72a1f981e24fc9c75972740bd0cb8
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
fs/ioctl.c