public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH STABLE 5.15 0/2] btrfs: raid56: backports to reduce corruption
Date: Fri, 19 Aug 2022 13:21:14 +0200	[thread overview]
Message-ID: <Yv9yKtRffK6tX8K5@kroah.com> (raw)
In-Reply-To: <cover.1660898037.git.wqu@suse.com>

On Fri, Aug 19, 2022 at 04:39:48PM +0800, Qu Wenruo wrote:
> This is the backport for v5.15.x stable branch.
> 
> The full explananation can be found here:
> https://lore.kernel.org/linux-btrfs/Yv85PTBsDhrQITZp@kroah.com/T/#t
> 
> Difference between v5.15.x and v5.18.x backports:
> 
> - btrfs_io_contrl::fs_info and btrfs_raid_bio::fs_info refactor
>   In v5.15 and older kernel, btrfs_raid_bio and btrfs_io_control both
>   have fs_info member, and the new rbio_add_bio() function utilizes
>   btrfs_io_ctrl::fs_info.
> 
>   Unfortunately that rbio->bioc->fs_info is not always initialized in
>   v5.15 and older kernels.
>   Thus has to use rbio->fs_info instead.
> 
>   If not properly handled, can lead to btrfs/158 crash.
> 
> 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
> 

All now queued up, thanks.

greg k-h

      parent reply	other threads:[~2022-08-19 11:21 UTC|newest]

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

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=Yv9yKtRffK6tX8K5@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=wqu@suse.com \
    /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