All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>,
	Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Subject: Re: KVM: MMU: handle invalid root_hpa at __direct_map
Date: Fri, 20 Dec 2013 19:22:57 +0100	[thread overview]
Message-ID: <52B48B01.5060706@redhat.com> (raw)
In-Reply-To: <20131219172850.GA22588@amt.cnet>

Il 19/12/2013 18:28, Marcelo Tosatti ha scritto:
> 
> It is possible for __direct_map to be called on invalid root_hpa
> (-1), two examples:
> 
> 1) try_async_pf -> can_do_async_pf
>     -> vmx_interrupt_allowed -> nested_vmx_vmexit
> 2) vmx_handle_exit -> vmx_interrupt_allowed -> nested_vmx_vmexit
> 
> Then to load_vmcs12_host_state and kvm_mmu_reset_context.
> 
> Check for this possibility, let fault exception be regenerated.
> 
> BZ: https://bugzilla.redhat.com/show_bug.cgi?id=924916
> 
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> 
> 
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index 40772ef..31a5702 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -2659,6 +2659,9 @@ static int __direct_map(struct kvm_vcpu *vcpu, gpa_t v, int write,
>  	int emulate = 0;
>  	gfn_t pseudo_gfn;
>  
> +	if (!VALID_PAGE(vcpu->arch.mmu.root_hpa))
> +		return 0;
> +
>  	for_each_shadow_entry(vcpu, (u64)gfn << PAGE_SHIFT, iterator) {
>  		if (iterator.level == level) {
>  			mmu_set_spte(vcpu, iterator.sptep, ACC_ALL,
> 

Applied to queue, thanks.

Paolo

  parent reply	other threads:[~2013-12-20 18:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 17:28 KVM: MMU: handle invalid root_hpa at __direct_map Marcelo Tosatti
2013-12-20  9:15 ` Xiao Guangrong
2013-12-20 12:59   ` Marcelo Tosatti
2013-12-20 18:22 ` Paolo Bonzini [this message]
     [not found] <CADs-y4TpXQ0zvg4p-_fkKkMDbEiho89hzhkSAYMEVAxbp63XzQ@mail.gmail.com>
2013-12-22 14:56 ` Marcelo Tosatti
2013-12-27 19:43   ` Marcelo Tosatti
2014-01-16 23:17     ` Rom Freiman
2014-01-17 21:39       ` Marcelo Tosatti

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=52B48B01.5060706@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=xiaoguangrong@linux.vnet.ibm.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.