xfs: make sure the rt allocator doesn't run off the end
authorDarrick J. Wong <darrick.wong@oracle.com>
Wed, 9 Sep 2020 21:21:06 +0000 (14:21 -0700)
committerDarrick J. Wong <darrick.wong@oracle.com>
Wed, 16 Sep 2020 03:52:42 +0000 (20:52 -0700)
commit2a6ca4baed620303d414934aa1b7b0a8e7bab05f
treea8c41f0884ede6e7a195d371176c26f6434e77bf
parent0f4ec0f157468fdb6512ccd9cd8cbb8b645fb4a0
xfs: make sure the rt allocator doesn't run off the end

There's an overflow bug in the realtime allocator.  If the rt volume is
large enough to handle a single allocation request that is larger than
the maximum bmap extent length and the rt bitmap ends exactly on a
bitmap block boundary, it's possible that the near allocator will try to
check the freeness of a range that extends past the end of the bitmap.
This fails with a corruption error and shuts down the fs.

Therefore, constrain maxlen so that the range scan cannot run off the
end of the rt bitmap.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
fs/xfs/xfs_rtalloc.c