On Wed, Apr 24, 2019 at 11:46:55AM +0300, Nikolay Borisov wrote:
> btrfs_trim_free_extents always caps the range it's going to trim based
> on the size of the device. This happens if find_first_clear_extent_bit
> detects that untrimmed range is past the last allocated range. Since it
> doesn't have knowledge of the size of the device it just returns (u64)-1
> for end. Then btrfs_trim_free_extents caps this to device->total_bytes.
> However, btrfs_trim_free_extent calculates 'len' based off of the
> actual usable end byte - in this case total_bytes - 1.
>
> Signed-off-by: Nikolay Borisov <nborisov@xxxxxxxx>
>
> Fixes: 4d877687cbbc ("btrfs: Switch btrfs_trim_free_extents to find_first_clear_extent_bit")
> ---
>
> David you might want to squash that in the 'Fixes' commit. With this I see
> generic/500 passing and also full xfstest didn't uncover any new regressions.
Folded, thanks.
