]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 30 Oct 2020 09:38:30 +0000 (10:38 +0100)
commite004f8f381e383a32b4df0eec60cc9813864cd92
tree6646106f903f53d94753619f0c290470061f66b8
parent7a1e074bc18d32718edcde0a0ad75fff262a4410
xfs: make sure the rt allocator doesn't run off the end

[ Upstream commit 2a6ca4baed620303d414934aa1b7b0a8e7bab05f ]

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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/xfs/xfs_rtalloc.c