linux.git/fs/btrfs/compression.c, branch v6.13

btrfs: use filemap_get_folio() helper

2024-11-11T13:34:19+00:00

When fgp_flags and gfp_flags are zero, use filemap_get_folio(A, B)
instead of __filemap_get_folio(A, B, 0, 0)—no need for the extra
arguments 0, 0.

Signed-off-by: Anand Jain 
Reviewed-by: David Sterba 
Signed-off-by: David Sterba

btrfs: rename btrfs_folio_(set|start|end)_writer_lock()

2024-11-11T13:34:18+00:00

Since there is no user of reader locks, rename the writer locks into a
more generic name, by removing the "_writer" part from the name.

And also rename btrfs_subpage::writer into btrfs_subpage::locked.

Signed-off-by: Qu Wenruo 
Reviewed-by: David Sterba 
Signed-off-by: David Sterba

btrfs: unify to use writer locks for subpage locking

2024-11-11T13:34:18+00:00

Since commit d7172f52e993 ("btrfs: use per-buffer locking for
extent_buffer reading"), metadata read no longer relies on the subpage
reader locking.

This means we do not need to maintain a different metadata/data split
for locking, so we can convert the existing reader lock users by:

- add_ra_bio_pages()
  Convert to btrfs_folio_set_writer_lock()

- end_folio_read()
  Convert to btrfs_folio_end_writer_lock()

- begin_folio_read()
  Convert to btrfs_folio_set_writer_lock()

- folio_range_has_eb()
  Remove the subpage->readers checks, since it is always 0.

- Remove btrfs_subpage_start_reader() and btrfs_subpage_end_reader()

Signed-off-by: Qu Wenruo 
Reviewed-by: David Sterba 
Signed-off-by: David Sterba

btrfs: drop unused parameter level from alloc_heuristic_ws()

2024-11-11T13:34:17+00:00

The compression heuristic pass does not need a level, so we can drop the
parameter.

Reviewed-by: Anand Jain 
Signed-off-by: David Sterba

btrfs: lzo: drop unused paramter level from lzo_alloc_workspace()

2024-11-11T13:34:16+00:00

The LZO compression has only one level, we don't need to pass the
parameter.

Reviewed-by: Anand Jain 
Signed-off-by: David Sterba

btrfs: compression: add an ASSERT() to ensure the read-in length is sane

2024-11-11T13:34:12+00:00

There are already two bugs (one in zlib, one in zstd) that involved
compression path is not handling sector size < page size cases well.

So it makes more sense to make sure that btrfs_compress_folios() returns

Since we already have two bugs (one in zlib, one in zstd) in the
compression path resulting the @total_in be to larger than the
to-be-compressed range length, there is enough reason to add an ASSERT()
to make sure the total read-in length doesn't exceed the input length.

Signed-off-by: Qu Wenruo 
Signed-off-by: David Sterba

btrfs: convert btrfs_decompress() to take a folio

2024-09-10T14:51:21+00:00

The old page API is being gradually replaced and converted to use folio
to improve code readability and avoid repeated conversion between page
and folio. Based on the previous patch, the compression path can be
directly used in folio without converting to page.

Signed-off-by: Li Zetao 
Reviewed-by: David Sterba 
Signed-off-by: David Sterba

btrfs: convert zstd_decompress() to take a folio

2024-09-10T14:51:21+00:00

The old page API is being gradually replaced and converted to use folio
to improve code readability and avoid repeated conversion between page
and folio. And memcpy_to_page() can be replaced with memcpy_to_folio().
But there is no memzero_folio(), but it can be replaced equivalently by
folio_zero_range().

Signed-off-by: Li Zetao 
Reviewed-by: David Sterba 
Signed-off-by: David Sterba

btrfs: convert lzo_decompress() to take a folio

2024-09-10T14:51:21+00:00

The old page API is being gradually replaced and converted to use folio
to improve code readability and avoid repeated conversion between page
and folio. And memcpy_to_page() can be replaced with memcpy_to_folio().
But there is no memzero_folio(), but it can be replaced equivalently by
folio_zero_range().

Signed-off-by: Li Zetao 
Reviewed-by: David Sterba 
Signed-off-by: David Sterba

btrfs: convert zlib_decompress() to take a folio

2024-09-10T14:51:21+00:00

The old page API is being gradually replaced and converted to use folio
to improve code readability and avoid repeated conversion between page
and folio. And memcpy_to_page() can be replaced with memcpy_to_folio().
But there is no memzero_folio(), but it can be replaced equivalently by
folio_zero_range().

Signed-off-by: Li Zetao 
Reviewed-by: David Sterba 
Signed-off-by: David Sterba