summaryrefslogtreecommitdiffstats
path: root/drivers/mtd/inftlmount.c
diff options
context:
space:
mode:
authorDarrick J. Wong <djwong@kernel.org>2021-08-11 02:00:30 +0200
committerDarrick J. Wong <djwong@kernel.org>2021-08-19 03:46:00 +0200
commitc02f6529864a4f5f91d216d324bac4ba75415d19 (patch)
tree1ae87318970ffb0e8afaa100a5833b476dd02a96 /drivers/mtd/inftlmount.c
parentxfs: drop ->writepage completely (diff)
downloadlinux-c02f6529864a4f5f91d216d324bac4ba75415d19.tar.xz
linux-c02f6529864a4f5f91d216d324bac4ba75415d19.zip
xfs: make xfs_rtalloc_query_range input parameters const
In commit 8ad560d2565e, we changed xfs_rtalloc_query_range to constrain the range of bits in the realtime bitmap file that would actually be searched. In commit a3a374bf1889, we changed the range again (incorrectly), leading to the fix in commit d88850bd5516, which finally corrected the range check code. Unfortunately, the author never noticed that the function modifies its input parameters, which is a totaly no-no since none of the other range query functions change their input parameters. So, fix this function yet again to stash the upper end of the query range (i.e. the high key) in a local variable and hope this is the last time I have to fix my own function. While we're at it, mark the key inputs const so nobody makes this mistake again. :( Fixes: 8ad560d2565e ("xfs: strengthen rtalloc query range checks") Not-fixed-by: a3a374bf1889 ("xfs: fix off-by-one error in xfs_rtalloc_query_range") Not-fixed-by: d88850bd5516 ("xfs: fix high key handling in the rt allocator's query_range function") Signed-off-by: Darrick J. Wong <djwong@kernel.org> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Chandan Babu R <chandanrlinux@gmail.com>
Diffstat (limited to 'drivers/mtd/inftlmount.c')
0 files changed, 0 insertions, 0 deletions