From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Kochera <kochera@google.com>
Cc: stable@vger.kernel.org
Subject: Re: Backport fix for CVE-2023-2124
Date: Tue, 6 Jun 2023 08:48:44 +0200 [thread overview]
Message-ID: <2023060655-superglue-occupier-80a9@gregkh> (raw)
In-Reply-To: <CAN1hJ_P+FG3ac4iV8AocZfffGC_dMUSZfpXKH4zPO1LS8+8RCQ@mail.gmail.com>
On Mon, Jun 05, 2023 at 03:54:54PM -0600, Michael Kochera wrote:
> Hello, the following patch cherry-picked cleanly during my testing.
>
> Subject of Patch: xfs: verify buffer contents when we skip log replay
> Commit Hash: 22ed903eee23a5b174e240f1cdfa9acf393a5210
> Reason why it should be applied: This fixes CVE-2023-2124.
> Kernel Versions to be applied to: 6.1, 5.15, 5.10
The xfs maintainers have their own process for getting patches into the
stable tree. Please at the least, cc: them in order so that they can
review the changes to see if they are relevant or not.
Did you test the above change that it solves the problem? If so, can
you provide a "Tested-by:" for it?
thanks,
greg k-h
prev parent reply other threads:[~2023-06-06 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 21:54 Backport fix for CVE-2023-2124 Michael Kochera
2023-06-06 6:48 ` 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=2023060655-superglue-occupier-80a9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kochera@google.com \
--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