Skip to content

btrfs: raid56: backports to reduce corruption

Qu Wenruo linux-btrfs stable 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 1 replyIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2btrfs: only write the sectors in the vertical stripe which has data stripesfs/btrfs/raid56.c+51 -40 replies
2/2btrfs: raid56: don't trust any cached sector in __raid56_parity_recover()fs/btrfs/raid56.c+6 -130 replies

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by.

PatchDavid Sterba
1/2A-b
2/2A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH STABLE 5.10 0/2] btrfs: raid56: backports to reduce corruption

This is the backport for v5.10.x stable branch.

The full explananation can be found here:
https://lore.kernel.org/linux-btrfs/[email protected]/

Difference between v5.10.x and v5.15.x backports:

- Naming change in btrfs_io_contrl
In v5.15, we don't have the btrfs_io_contrl rename, thus only btrfs_bio.

- Missing btrfs_fs_info::sectorsize_bits
Since RAID56 doesn't support anything but PAGE_SIZE == sectorsize (until v5.19+), here we just use PAGE_SHIFT.

Another thing related to v5.10.x testing is, there are some lockdep assert triggered related to uuid_mutex.

I'm not 100% sure, but at least RAID56 code is not touching that mutex, thus I guess it's some other problems.

Qu Wenruo (2):
btrfs: only write the sectors in the vertical stripe which has data
stripes
btrfs: raid56: don't trust any cached sector in

    __raid56_parity_recover()
 fs/btrfs/raid56.c | 74 ++++++++++++++++++++++++++++++++++++-----------
 1 file changed, 57 insertions(+), 17 deletions(-)
Signature · 1 line
2.37.1