diff options
| author | Nikolay Borisov <nborisov@suse.com> | 2019-06-03 12:06:01 +0200 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2019-07-01 13:35:02 +0200 |
| commit | 53460a4572585b508dc4cb6f09653ac50ba3fc49 (patch) | |
| tree | 1b4b4840274da456c3f75d27d4b7428df1c1eb0d /fs/btrfs/tests | |
| parent | btrfs: use file:line format for assertion report (diff) | |
| download | linux-53460a4572585b508dc4cb6f09653ac50ba3fc49.tar.xz linux-53460a4572585b508dc4cb6f09653ac50ba3fc49.zip | |
btrfs: trim: make reserved device area adjustments more explicit
Currently the first megabyte on a device housing a btrfs filesystem is
exempt from allocation and trimming. Currently this is not a problem
since 'start' is set to 1M at the beginning of btrfs_trim_free_extents
and find_first_clear_extent_bit always returns a range that is >= start.
However, in a follow up patch find_first_clear_extent_bit will be
changed such that it will return a range containing 'start' and this
range may very well be 0...>=1M so 'start'.
Future proof the sole user of find_first_clear_extent_bit by setting
'start' after the function is called. No functional changes.
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/tests')
0 files changed, 0 insertions, 0 deletions