From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH STABLE 5.4 0/2] btrfs: raid56: backports to reduce corruption
Date: Sat, 20 Aug 2022 14:34:58 +0800 [thread overview]
Message-ID: <cover.1660977189.git.wqu@suse.com> (raw)
This is the backport for v5.4.x stable branch.
The full explananation can be found here:
https://lore.kernel.org/linux-btrfs/cover.1660891713.git.wqu@suse.com/
These backport have no change compared to v5.10.x backports (at least
nothing git can not auto-resolve).
While the testing part shows some extra warning in btrfs/162, it's the
existing show_dev_name related RCU string accesss problem, not something
new regression caused by these backports.
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
next reply other threads:[~2022-08-20 6:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 6:34 Qu Wenruo [this message]
2022-08-20 6:34 ` [PATCH STABLE 5.4 1/2] btrfs: only write the sectors in the vertical stripe which has data stripes Qu Wenruo
2022-08-20 6:35 ` [PATCH STABLE 5.4 2/2] btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() Qu Wenruo
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.1660977189.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.