diff options
| author | Josef Bacik <josef@toxicpanda.com> | 2021-11-22 17:04:19 -0500 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2021-12-08 15:42:24 +0100 |
| commit | f981fec12cc5d2c07942301744b9ea61228bf246 (patch) | |
| tree | 1dd5ecf9deec621a01a125ab0025d327196fdc03 /fs/btrfs/extent_io.c | |
| parent | d815b3f2f273537cb8afaf5ab11a46851f6c03e5 (diff) | |
| download | linux-f981fec12cc5d2c07942301744b9ea61228bf246.tar.bz2 | |
btrfs: fail if fstrim_range->start == U64_MAX
We've always been failing generic/260 because it's testing things we
actually don't care about and thus won't fail for. However we probably
should fail for fstrim_range->start == U64_MAX since we clearly can't
trim anything past that. This in combination with an update to
generic/260 will allow us to pass this test properly.
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/extent_io.c')
0 files changed, 0 insertions, 0 deletions