From: Mathias Krause <minipli@grsecurity.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
lwn@lwn.net, jslaby@suse.cz,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: Linux 5.15.103
Date: Tue, 28 Mar 2023 14:29:11 +0200 [thread overview]
Message-ID: <f86cb36e-b331-8b8d-f087-5e2e8a5ae962@grsecurity.net> (raw)
In-Reply-To: <ZCLaLWJiIsDV5yGr@kroah.com>
On 28.03.23 14:14, Greg Kroah-Hartman wrote:
> 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 :(
Neither were any of the above commits. o.O
Commit 3e48a6349d29 ("KVM: Optimize kvm_make_vcpus_request_mask() a
bit") has this tag, though:
Stable-dep-of: 2b0128127373 ("KVM: Register /dev/kvm as the _very_ last
thing during initialization")
I don't know why, though. These two commits have little in common.
Maybe Sasha knows why?
>
> Have now done so, thanks.
Thanks!
Mathias
next prev parent reply other threads:[~2023-03-28 12:29 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
2023-03-28 12:29 ` Mathias Krause [this message]
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=f86cb36e-b331-8b8d-f087-5e2e8a5ae962@grsecurity.net \
--to=minipli@grsecurity.net \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=pbonzini@redhat.com \
--cc=sashal@kernel.org \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vkuznets@redhat.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;
as well as URLs for NNTP newsgroup(s).