[GIT PULL] iomap: bug fix for 5.7-rc3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Linus,

Please pull this single bug fix for 5.7 that hoists the check for an
unrepresentable FIBMAP return value into ioctl_fibmap.  The internal
kernel function can handle 64-bit values (and is needed to fix a
regression on ext4 + jbd2); it is only the userspace ioctl that is so
old that it cannot deal.  The branch merged cleanly with upstream head
as of a few minutes ago.

--D

The following changes since commit 6a8b55ed4056ea5559ebe4f6a4b247f627870d4c:

  Linux 5.7-rc3 (2020-04-26 13:51:02 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-5.7-fixes-1

for you to fetch changes up to b75dfde1212991b24b220c3995101c60a7b8ae74:

  fibmap: Warn and return an error in case of block > INT_MAX (2020-04-30 07:57:46 -0700)

----------------------------------------------------------------
Changes for 5.7:
- Move the FIBMAP range check and warning out of the backend iomap
implementation and into the frontend ioctl_fibmap so that the checking
is consistent for all implementations.

----------------------------------------------------------------
Ritesh Harjani (1):
      fibmap: Warn and return an error in case of block > INT_MAX

 fs/ioctl.c        | 8 ++++++++
 fs/iomap/fiemap.c | 5 +----
 2 files changed, 9 insertions(+), 4 deletions(-)



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux