From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-kernel 2/2] cherry-pick fix for uefi guests hanging upon guest-initialized reboot
Date: Fri, 25 Aug 2023 09:40:46 +0200 [thread overview]
Message-ID: <c486d8b3-6665-cf42-9563-1b3fb9e86184@proxmox.com> (raw)
In-Reply-To: <2c536056-ee40-59b2-5197-d5dcb6730f4f@proxmox.com>
On 8/25/23 09:35, Fiona Ebner wrote:
> The mentioned commits and reading in the mail thread
>
>>> Cc: stable@vger.kernel.org # v5.13+
>>> Fixes: 3039bcc74498 ("KVM: Move x86's MMU notifier memslot walkers to generic code")
>>
>> This Fixes isn't correct. That change only affected x86, which doesn't have this
>> bug. And looking at commit cd4c71835228 ("KVM: arm64: Convert to the gfn-based MMU
>> notifier callbacks"), arm64 did NOT skip invalid slots
>
> unfortunately make it sound like it's not an x86 issue. But who knows? I
> guess it won't hurt in either case, as it's already in upstream stable.
>
Also looks like the affected systems do not have KSM turned on either
way, so it's quite unlikely to be the fix at this point.
prev parent reply other threads:[~2023-08-25 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 14:30 [pve-devel] [PATCH pve-kernel 0/2] cherry-pick a patch from kernel.org stable 5.15 for guests hanging during reboot Stoiko Ivanov
2023-08-24 14:30 ` [pve-devel] [PATCH pve-kernel 1/2] refresh patches after ./debian/scripts/export-patchqueue Stoiko Ivanov
2023-08-24 14:30 ` [pve-devel] [PATCH pve-kernel 2/2] cherry-pick fix for uefi guests hanging upon guest-initialized reboot Stoiko Ivanov
2023-08-25 7:35 ` Fiona Ebner
2023-08-25 7:40 ` Stefan Hanreich [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=c486d8b3-6665-cf42-9563-1b3fb9e86184@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.