| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <169759163972.1787364.3932584247097617727.b4-ty@google.com>
Date: Tue, 17 Oct 2023 18:16:20 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, kvm@...r.kernel.org,
Nicolas Saenz Julienne <nsaenz@...zon.com>
Cc: vkuznets@...hat.com, pbonzini@...hat.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com, graf@...zon.de, rkagan@...zon.de,
linux-kernel@...r.kernel.org, anelkz@...zon.de,
stable@...r.kernel.org
Subject: Re: [PATCH v3] KVM: x86: hyper-v: Don't auto-enable stimer on write
from user-space
On Tue, 17 Oct 2023 15:51:02 +0000, Nicolas Saenz Julienne wrote:
> Don't apply the stimer's counter side effects when modifying its
> value from user-space, as this may trigger spurious interrupts.
>
> For example:
> - The stimer is configured in auto-enable mode.
> - The stimer's count is set and the timer enabled.
> - The stimer expires, an interrupt is injected.
> - The VM is live migrated.
> - The stimer config and count are deserialized, auto-enable is ON, the
> stimer is re-enabled.
> - The stimer expires right away, and injects an unwarranted interrupt.
>
> [...]
Applied to kvm-x86 misc, thanks!
[1/1] KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space
https://github.com/kvm-x86/linux/commit/d6800af51c76
--
https://github.com/kvm-x86/linux/tree/next
Powered by blists - more mailing lists