public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH v3] KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space
@ 2023-10-17 15:51 Nicolas Saenz Julienne
  2023-10-17 16:02 ` Vitaly Kuznetsov
  2023-10-18  1:16 ` Sean Christopherson
  0 siblings, 2 replies; 3+ messages in thread
From: Nicolas Saenz Julienne @ 2023-10-17 15:51 UTC (permalink / raw)
  To: kvm
  Cc: vkuznets, seanjc, pbonzini, tglx, mingo, bp, dave.hansen, x86,
	hpa, graf, rkagan, linux-kernel, anelkz, Nicolas Saenz Julienne,
	stable

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.

Cc: stable@vger.kernel.org
Fixes: 1f4b34f825e8 ("kvm/x86: Hyper-V SynIC timers")
Signed-off-by: Nicolas Saenz Julienne <nsaenz@amazon.com>
---

Changes since v2: 
- reword commit message/subject.

Changes since v1:
- Cover all 'stimer->config.enable' updates.

 arch/x86/kvm/hyperv.c | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
index 7c2dac6824e2..238afd7335e4 100644
--- a/arch/x86/kvm/hyperv.c
+++ b/arch/x86/kvm/hyperv.c
@@ -727,10 +727,12 @@ static int stimer_set_count(struct kvm_vcpu_hv_stimer *stimer, u64 count,
 
 	stimer_cleanup(stimer);
 	stimer->count = count;
-	if (stimer->count == 0)
-		stimer->config.enable = 0;
-	else if (stimer->config.auto_enable)
-		stimer->config.enable = 1;
+	if (!host) {
+		if (stimer->count == 0)
+			stimer->config.enable = 0;
+		else if (stimer->config.auto_enable)
+			stimer->config.enable = 1;
+	}
 
 	if (stimer->config.enable)
 		stimer_mark_pending(stimer, false);
-- 
2.40.1


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH v3] KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space
  2023-10-17 15:51 [PATCH v3] KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space Nicolas Saenz Julienne
@ 2023-10-17 16:02 ` Vitaly Kuznetsov
  2023-10-18  1:16 ` Sean Christopherson
  1 sibling, 0 replies; 3+ messages in thread
From: Vitaly Kuznetsov @ 2023-10-17 16:02 UTC (permalink / raw)
  To: Nicolas Saenz Julienne, kvm
  Cc: seanjc, pbonzini, tglx, mingo, bp, dave.hansen, x86, hpa, graf,
	rkagan, linux-kernel, anelkz, Nicolas Saenz Julienne, stable

Nicolas Saenz Julienne <nsaenz@amazon.com> writes:

> 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.
>
> Cc: stable@vger.kernel.org
> Fixes: 1f4b34f825e8 ("kvm/x86: Hyper-V SynIC timers")
> Signed-off-by: Nicolas Saenz Julienne <nsaenz@amazon.com>
> ---
>
> Changes since v2: 
> - reword commit message/subject.
>
> Changes since v1:
> - Cover all 'stimer->config.enable' updates.
>
>  arch/x86/kvm/hyperv.c | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
> index 7c2dac6824e2..238afd7335e4 100644
> --- a/arch/x86/kvm/hyperv.c
> +++ b/arch/x86/kvm/hyperv.c
> @@ -727,10 +727,12 @@ static int stimer_set_count(struct kvm_vcpu_hv_stimer *stimer, u64 count,
>  
>  	stimer_cleanup(stimer);
>  	stimer->count = count;
> -	if (stimer->count == 0)
> -		stimer->config.enable = 0;
> -	else if (stimer->config.auto_enable)
> -		stimer->config.enable = 1;
> +	if (!host) {
> +		if (stimer->count == 0)
> +			stimer->config.enable = 0;
> +		else if (stimer->config.auto_enable)
> +			stimer->config.enable = 1;
> +	}
>  
>  	if (stimer->config.enable)
>  		stimer_mark_pending(stimer, false);

LGTM, thanks!

Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>

-- 
Vitaly


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v3] KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space
  2023-10-17 15:51 [PATCH v3] KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space Nicolas Saenz Julienne
  2023-10-17 16:02 ` Vitaly Kuznetsov
@ 2023-10-18  1:16 ` Sean Christopherson
  1 sibling, 0 replies; 3+ messages in thread
From: Sean Christopherson @ 2023-10-18  1:16 UTC (permalink / raw)
  To: Sean Christopherson, kvm, Nicolas Saenz Julienne
  Cc: vkuznets, pbonzini, tglx, mingo, bp, dave.hansen, x86, hpa, graf,
	rkagan, linux-kernel, anelkz, stable

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-10-18  1:17 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-10-17 15:51 [PATCH v3] KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space Nicolas Saenz Julienne
2023-10-17 16:02 ` Vitaly Kuznetsov
2023-10-18  1:16 ` Sean Christopherson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox