diff options
author | Darrick J. Wong <darrick.wong@oracle.com> | 2020-09-10 00:21:06 +0300 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-10-29 12:08:25 +0300 |
commit | 0c0476d096d69e20bbaf5cebe78d0419d49f10df (patch) | |
tree | b61830f3704159c6857a27b54795e703a85569f6 /drivers/usb/host | |
parent | 0c35ab58c587b1e812908c524c25850506d75b42 (diff) | |
download | linux-0c0476d096d69e20bbaf5cebe78d0419d49f10df.tar.xz |
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>
Diffstat (limited to 'drivers/usb/host')
0 files changed, 0 insertions, 0 deletions