From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alistair Delva <adelva@google.com>
Cc: Sasha Levin <sashal@kernel.org>,
Elie Kheirallah <khei@google.com>,
Frederick Mayle <fmayle@google.com>,
Cody Schuffelen <schuffelen@google.com>,
"Cc: Android Kernel" <kernel-team@android.com>,
Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: 916b7f42b3b3 to 6.12 (was Re: 2a23a4e1159c to 6.12)
Date: Fri, 22 Aug 2025 17:51:10 +0200 [thread overview]
Message-ID: <2025082202-civil-appraisal-852a@gregkh> (raw)
In-Reply-To: <CANDihLEu2dMMpYdQxJK4q7YAqqiwdroH8J7q+w6FmhX7mcQQuQ@mail.gmail.com>
On Fri, Aug 22, 2025 at 08:35:07AM -0700, Alistair Delva wrote:
> On Thu, Aug 21, 2025 at 11:32 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Aug 19, 2025 at 03:00:25PM -0700, Alistair Delva wrote:
> > > Dear stable maintainers,
> > >
> > > Please consider cherry-picking 2a23a4e1159c ("kvm:
> > > retrynx_huge_page_recovery_thread creation") to 6.12. It fixes
> > > a problem where some VMMs (crosvm, firecracker, others) may
> > > unnecessarily terminate a VM when -ENOMEM is returned to
> > > userspace for a non-fatal condition.
> >
> > That is not a valid commit in Linus's tree, are you sure it is correct?
>
> Sorry, the commit is actually 916b7f42b3b3.
Much better, now queued up.
prev parent reply other threads:[~2025-08-22 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 22:00 2a23a4e1159c to 6.12 Alistair Delva
2025-08-22 6:32 ` Greg Kroah-Hartman
2025-08-22 15:35 ` 916b7f42b3b3 to 6.12 (was Re: 2a23a4e1159c to 6.12) Alistair Delva
2025-08-22 15:51 ` Greg Kroah-Hartman [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=2025082202-civil-appraisal-852a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=adelva@google.com \
--cc=fmayle@google.com \
--cc=kernel-team@android.com \
--cc=khei@google.com \
--cc=sashal@kernel.org \
--cc=schuffelen@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