From: Greg KH <greg@kroah.com>
To: Qu Wenruo <wqu@suse.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Subject: Re: Patch "btrfs: allow buffered write to avoid full page read if it's block aligned" has been added to the 6.14-stable tree
Date: Fri, 23 May 2025 06:52:28 +0200 [thread overview]
Message-ID: <2025052321-prepay-defog-2986@gregkh> (raw)
In-Reply-To: <6377b61b-c16e-4d10-becc-53ac4af72725@suse.com>
On Fri, May 23, 2025 at 06:51:18AM +0930, Qu Wenruo wrote:
>
>
> 在 2025/5/23 06:35, Sasha Levin 写道:
> > This is a note to let you know that I've just added the patch titled
> >
> > btrfs: allow buffered write to avoid full page read if it's block aligned
> >
> > to the 6.14-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > btrfs-allow-buffered-write-to-avoid-full-page-read-i.patch
> > and it can be found in the queue-6.14 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Please drop this patch from all stable branches.
>
> Although this patch mentions a failure in fstests, it acts more like an
> optimization for btrfs.
>
> Furthermore it relies quite some patches that may not be in stable kernels.
>
> Without all the dependency, this can lead to data corruption.
>
> Please drop this one from all stable kernels.
Now dropped, thanks.
greg k-h
prev parent reply other threads:[~2025-05-23 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250522210549.3118269-1-sashal@kernel.org>
2025-05-22 21:21 ` Patch "btrfs: allow buffered write to avoid full page read if it's block aligned" has been added to the 6.14-stable tree Qu Wenruo
2025-05-23 4:52 ` 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=2025052321-prepay-defog-2986@gregkh \
--to=greg@kroah.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=stable-commits@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