diff options
| author | Filipe Manana <[email protected]> | 2024-02-29 10:37:04 +0000 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2024-03-05 18:11:07 +0100 |
| commit | ae6bd7f9b46a29af52ebfac25d395757e2031d0d (patch) | |
| tree | f3359e6efbab5b57269bcbf38e7091cd80623e0d /scripts/generate_rust_analyzer.py | |
| parent | b20fe56cd285dbbf64874ec9d1c81f8a8ac2f821 (diff) | |
btrfs: fix off-by-one chunk length calculation at contains_pending_extent()
At contains_pending_extent() the value of the end offset of a chunk we
found in the device's allocation state io tree is inclusive, so when
we calculate the length we pass to the in_range() macro, we must sum
1 to the expression "physical_end - physical_offset".
In practice the wrong calculation should be harmless as chunks sizes
are never 1 byte and we should never have 1 byte ranges of unallocated
space. Nevertheless fix the wrong calculation.
Reported-by: Alex Lyakas <[email protected]>
Link: https://lore.kernel.org/linux-btrfs/CAOcd+r30e-f4R-5x-S7sV22RJPe7+pgwherA6xqN2_qe7o4XTg@mail.gmail.com/
Fixes: 1c11b63eff2a ("btrfs: replace pending/pinned chunks lists with io tree")
CC: [email protected] # 6.1+
Reviewed-by: Josef Bacik <[email protected]>
Reviewed-by: Qu Wenruo <[email protected]>
Signed-off-by: Filipe Manana <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions