public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH STABLE 5.10 0/2] btrfs: raid56: backports to reduce corruption
Date: Fri, 19 Aug 2022 20:01:08 +0800	[thread overview]
Message-ID: <cover.1660906975.git.wqu@suse.com> (raw)

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

The full explananation can be found here:
https://lore.kernel.org/linux-btrfs/cover.1660891713.git.wqu@suse.com/

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(-)

-- 
2.37.1


             reply	other threads:[~2022-08-19 12:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 12:01 Qu Wenruo [this message]
2022-08-19 12:01 ` [PATCH STABLE 5.10 1/2] btrfs: only write the sectors in the vertical stripe which has data stripes Qu Wenruo
2022-08-19 12:01 ` [PATCH STABLE 5.10 2/2] btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() Qu Wenruo
2022-08-19 14:39 ` [PATCH STABLE 5.10 0/2] btrfs: raid56: backports to reduce corruption Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1660906975.git.wqu@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox