From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mathias Krause <minipli@grsecurity.net>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 5.15.103
Date: Tue, 28 Mar 2023 14:14:37 +0200 [thread overview]
Message-ID: <ZCLaLWJiIsDV5yGr@kroah.com> (raw)
In-Reply-To: <c359c777-c3af-b4a6-791d-d51916160bf5@grsecurity.net>
On Tue, Mar 28, 2023 at 02:02:03PM +0200, Mathias Krause wrote:
> On 17.03.23 09:04, Greg Kroah-Hartman wrote:
> > I'm announcing the release of the 5.15.103 kernel.
> >
> > [...]
> >
> > Vitaly Kuznetsov (4):
> > KVM: Optimize kvm_make_vcpus_request_mask() a bit
> > KVM: Pre-allocate cpumasks for kvm_make_all_cpus_request_except()
> > KVM: nVMX: Don't use Enlightened MSR Bitmap for L3
> > KVM: VMX: Introduce vmx_msr_bitmap_l01_changed() helper
> >
>
> That list is missing commit 6470accc7ba9 ("KVM: x86: hyper-v: Avoid
> calling kvm_make_vcpus_request_mask() with vcpu_mask==NULL") to fulfill
> the prerequisite of "KVM: Optimize kvm_make_vcpus_request_mask() a bit".
>
> Right now the kvm selftests trigger a kernel NULL deref for the hyperv
> test, making the system hang.
>
> Please consider applying commit 6470accc7ba9 for the next v5.15.x release.
It wasn't tagged for the stable kernels, so we didn't pick it up :(
Have now done so, thanks.
greg k-h
next prev parent reply other threads:[~2023-03-28 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 8:04 Linux 5.15.103 Greg Kroah-Hartman
2023-03-17 8:04 ` Greg Kroah-Hartman
2023-03-28 12:02 ` Mathias Krause
2023-03-28 12:14 ` Greg Kroah-Hartman [this message]
2023-03-28 12:29 ` Mathias Krause
2023-04-01 13:23 ` Sasha Levin
2023-04-03 6:51 ` Mathias Krause
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=ZCLaLWJiIsDV5yGr@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=minipli@grsecurity.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 NNTP newsgroup(s).