From: Greg KH <gregkh@linuxfoundation.org>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, stable@vger.kernel.org,
David Sterba <dsterba@suse.com>
Subject: Re: [PATCH STABLE 5.19 0/2] btrfs: raid56: backports to reduce corruption
Date: Fri, 19 Aug 2022 09:18:21 +0200 [thread overview]
Message-ID: <Yv85PTBsDhrQITZp@kroah.com> (raw)
In-Reply-To: <ee7c8476-7c93-100d-a0ff-441b71f61e6a@suse.com>
On Fri, Aug 19, 2022 at 03:08:07PM +0800, Qu Wenruo wrote:
> BTW, since I have to re-run all the tests for every stable branch, for the
> stable branches and 5.18.x backports may be delayed a little.
>
> In that case, I guess I should submit backports in the most recent stable
> branches first?
Yes please as we can not take patches only into older trees if the same
fix is not already in newer trees as you do not want someone to upgrade
and hit a regression.
thanks,
greg k-h
prev parent reply other threads:[~2022-08-19 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 7:01 [PATCH STABLE 5.19 0/2] btrfs: raid56: backports to reduce corruption Qu Wenruo
2022-08-19 7:01 ` [PATCH STABLE 5.19 1/2] btrfs: only write the sectors in the vertical stripe which has data stripes Qu Wenruo
2022-08-19 7:01 ` [PATCH STABLE 5.19 2/2] btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() Qu Wenruo
2022-08-19 7:08 ` [PATCH STABLE 5.19 0/2] btrfs: raid56: backports to reduce corruption Qu Wenruo
2022-08-19 7:18 ` 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=Yv85PTBsDhrQITZp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dsterba@suse.com \
--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