From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: stable@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Jintao Yin <nicememory@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Please apply "ext4,f2fs: fix readahead of verity data" to stable
Date: Tue, 8 Nov 2022 13:19:09 +0100 [thread overview]
Message-ID: <Y2pJPTSzgnNk37oA@kroah.com> (raw)
In-Reply-To: <Y2lL+lSibGY9hPEE@sol.localdomain>
On Mon, Nov 07, 2022 at 10:18:34AM -0800, Eric Biggers wrote:
> Stable maintainers,
>
> Please apply commit 4fa0e3ff217f775cb58d2d6d51820ec519243fb9
> ("ext4,f2fs: fix readahead of verity data") to stable, 5.10 and later. It
> cherry-picks cleanly to 6.0 and 5.15. I'll send it out manually for 5.10.
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-11-08 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 18:18 Please apply "ext4,f2fs: fix readahead of verity data" to stable Eric Biggers
2022-11-08 12:19 ` 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=Y2pJPTSzgnNk37oA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=nicememory@gmail.com \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).