diff options
| author | Nikolay Borisov <[email protected]> | 2019-06-03 13:06:02 +0300 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2019-07-01 13:35:02 +0200 |
| commit | 1eaebb341d2b4183d0112b76e31ccff3e1fe3092 (patch) | |
| tree | 91ab17f1a296d66d5707c5063f1a61084611ae0d /tools/perf/scripts | |
| parent | 53460a4572585b508dc4cb6f09653ac50ba3fc49 (diff) | |
btrfs: Don't trim returned range based on input value in find_first_clear_extent_bit
Currently find_first_clear_extent_bit always returns a range whose
starting value is >= passed 'start'. This implicit trimming behavior is
somewhat subtle and an implementation detail.
Instead, this patch modifies the function such that now it always
returns the range which contains passed 'start' and has the given bits
unset. This range could either be due to presence of existing records
which contains 'start' but have the bits unset or because there are no
records that contain the given starting offset.
This patch also adds test cases which cover find_first_clear_extent_bit
since they were missing up until now.
Reviewed-by: Qu Wenruo <[email protected]>
Signed-off-by: Nikolay Borisov <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'tools/perf/scripts')
0 files changed, 0 insertions, 0 deletions