diff options
author | Luca Stefani <luca.stefani.ge1@gmail.com> | 2024-09-17 23:33:05 +0300 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2024-10-08 00:21:56 +0300 |
commit | 69313850dce33ce8c24b38576a279421f4c60996 (patch) | |
tree | 018fa34b1d6dc82cc1379a9b3c76b3c2f6e018ae /fs/squashfs/zstd_wrapper.c | |
parent | a99fcb0158978ed332009449b484e5f3ca2d7df4 (diff) | |
download | linux-69313850dce33ce8c24b38576a279421f4c60996.tar.xz |
btrfs: add cancellation points to trim loops
There are reports that system cannot suspend due to running trim because
the task responsible for trimming the device isn't able to finish in
time, especially since we have a free extent discarding phase, which can
trim a lot of unallocated space. There are no limits on the trim size
(unlike the block group part).
Since trime isn't a critical call it can be interrupted at any time,
in such cases we stop the trim, report the amount of discarded bytes and
return an error.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=219180
Link: https://bugzilla.suse.com/show_bug.cgi?id=1229737
CC: stable@vger.kernel.org # 5.15+
Signed-off-by: Luca Stefani <luca.stefani.ge1@gmail.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/squashfs/zstd_wrapper.c')
0 files changed, 0 insertions, 0 deletions