mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: 黄乐 <huangle1@jd.com>, "vkuznets@redhat.com" <vkuznets@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] KVM: x86: Fix uninitialized eoi_exit_bitmap usage in vcpu_load_eoi_exitmap()
Date: Tue, 16 Nov 2021 10:44:17 +0100	[thread overview]
Message-ID: <b455d273-ef5e-bc78-ac31-2543499324b6@redhat.com> (raw)
In-Reply-To: <62115b277dab49ea97da5633f8522daf@jd.com>

On 11/15/21 15:08, 黄乐 wrote:
> In vcpu_load_eoi_exitmap(), currently the eoi_exit_bitmap[4] array is
> initialized only when Hyper-V context is available, in other path it is
> just passed to kvm_x86_ops.load_eoi_exitmap() directly from on the stack,
> which would cause unexpected interrupt delivery/handling issues, e.g. an
> *old* linux kernel that relies on PIT to do clock calibration on KVM might
> randomly fail to boot.
> 
> Fix it by passing ioapic_handled_vectors to load_eoi_exitmap() when Hyper-V
> context is not available.
> 
> Fixes: f2bc14b69c38 ("KVM: x86: hyper-v: Prepare to meet unallocated Hyper-V context")
> Cc: stable@vger.kernel.org
> Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> Signed-off-by: Huang Le <huangle1@jd.com>
> ---
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index dc7eb5fddfd3..26466f94e31a 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -9547,12 +9547,16 @@ static void vcpu_load_eoi_exitmap(struct kvm_vcpu *vcpu)
>   	if (!kvm_apic_hw_enabled(vcpu->arch.apic))
>   		return;
>   
> -	if (to_hv_vcpu(vcpu))
> +	if (to_hv_vcpu(vcpu)) {
>   		bitmap_or((ulong *)eoi_exit_bitmap,
>   			  vcpu->arch.ioapic_handled_vectors,
>   			  to_hv_synic(vcpu)->vec_bitmap, 256);
> +		static_call(kvm_x86_load_eoi_exitmap)(vcpu, eoi_exit_bitmap);
> +		return;
> +	}
>   
> -	static_call(kvm_x86_load_eoi_exitmap)(vcpu, eoi_exit_bitmap);
> +	static_call(kvm_x86_load_eoi_exitmap)(
> +		vcpu, (u64 *)vcpu->arch.ioapic_handled_vectors);
>   }
>   
>   void kvm_arch_mmu_notifier_invalidate_range(struct kvm *kvm,
> 

Queued, thanks.

Paolo


      reply	other threads:[~2021-11-16  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 14:08 黄乐
2021-11-16  9:44 ` Paolo Bonzini [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=b455d273-ef5e-bc78-ac31-2543499324b6@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=huangle1@jd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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

all inboxes | Powered by JetHome®