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 4.14 0/2] btrfs: raid56: backporst to reduce corruption
Date: Sat, 20 Aug 2022 16:49:21 +0800	[thread overview]
Message-ID: <cover.1660985049.git.wqu@suse.com> (raw)

This is the backport for v4.19.x stable branch.

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

No code change between v4.14.x and v4.19.x, at least nothing git can not
auto-resolve.

Testing wise, this is beyond my testing environment.
Although latest GCC compiles without problem, the result kernel can not
be properly boot at all, not even any kernel early boot message.

I'm not sure if this is something related to latest edk2 UEFI or
something else, I can no longer do proper testing for any older branch,
including this 4.19 one.

Thus I can not do any guarantee on these backports, unfortunately
the backports can only go to v5.x branches for now.

Unless anyone has better ideas how to build and run older kernels with
latest edk2 UEFI environment.

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-20  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20  8:49 Qu Wenruo [this message]
2022-08-20  8:49 ` [PATCH STABLE 4.14 1/2] btrfs: only write the sectors in the vertical stripe which has data stripes Qu Wenruo
2022-08-20  8:49 ` [PATCH STABLE 4.14 2/2] btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() Qu Wenruo
2022-08-23  7:24 ` [PATCH STABLE 4.14 0/2] btrfs: raid56: backporst 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.1660985049.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