Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755088AbdGSPOq (ORCPT ); Wed, 19 Jul 2017 11:14:46 -0400 Received: from mail-pf0-f196.google.com ([209.85.192.196]:36453 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754505AbdGSPOm (ORCPT ); Wed, 19 Jul 2017 11:14:42 -0400 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [PATCH] KVM: VMX: Fix invalid guest state detection after task-switch emulation From: Nadav Amit In-Reply-To: <20170719112926.GA13502@potion> Date: Wed, 19 Jul 2017 08:14:39 -0700 Cc: Wanpeng Li , "linux-kernel@vger.kernel.org" , kvm , Paolo Bonzini , Wanpeng Li Message-Id: References: <1499757180-20439-1-git-send-email-wanpeng.li@hotmail.com> <20170719112926.GA13502@potion> To: =?utf-8?B?UmFkaW0gS3LEjW3DocWZ?= X-Mailer: Apple Mail (2.3273) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nfs id v6JFEp2Y006047 Content-Length: 2271 Lines: 63 Radim Krčmář wrote: > 2017-07-19 13:34+0800, Wanpeng Li: >> Ping, :) > > I misunderstood where the ball is ... is the patch below ok? > > ---8<--- > This can be reproduced by EPT=1, unrestricted_guest=N, emulate_invalid_state=Y > or EPT=0, the trace of kvm-unit-tests/taskswitch2.flat is like below, it > tries to emulate invalid guest state task-switch: > > kvm_exit: reason TASK_SWITCH rip 0x0 info 40000058 0 > kvm_emulate_insn: 42000:0:0f 0b (0x2) > kvm_emulate_insn: 42000:0:0f 0b (0x2) failed > kvm_inj_exception: #UD (0x0) > kvm_entry: vcpu 0 > kvm_exit: reason TASK_SWITCH rip 0x0 info 40000058 0 > kvm_emulate_insn: 42000:0:0f 0b (0x2) > kvm_emulate_insn: 42000:0:0f 0b (0x2) failed > kvm_inj_exception: #UD (0x0) > > It appears that the task-switch emulation updates rflags (and vm86 flag) > only after the segments are loaded, causing vmx->emulation_required to > be set, when in fact invalid guest state emulation is not needed. > > This patch fixes it by updating vmx->emulation_required after the rflags > (and vm86 flag) is updated. > > Suggested-by: Nadav Amit > Signed-off-by: Wanpeng Li > [Wanpeng wrote the commit message with initial patch and Radim moved the > update to vmx_set_rflags and added Paolo's suggestion for the check.] > Signed-off-by: Radim Krčmář > --- > arch/x86/kvm/vmx.c | 15 ++++++++++----- > 1 file changed, 10 insertions(+), 5 deletions(-) > > diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c > index 84e62acf2dd8..a776aea0043a 100644 > --- a/arch/x86/kvm/vmx.c > +++ b/arch/x86/kvm/vmx.c > @@ -2326,6 +2326,11 @@ static void vmx_vcpu_put(struct kvm_vcpu *vcpu) > __vmx_load_host_state(to_vmx(vcpu)); > } > > +static bool emulation_required(struct kvm_vcpu *vcpu) > +{ > + return emulate_invalid_guest_state && !guest_state_valid(vcpu); > +} > + > static void vmx_decache_cr0_guest_bits(struct kvm_vcpu *vcpu); > > /* > @@ -2363,6 +2368,8 @@ static unsigned long vmx_get_rflags(struct kvm_vcpu *vcpu) > > static void vmx_set_rflags(struct kvm_vcpu *vcpu, unsigned long rflags) > { > + unsigned long old_rflags = to_vmx(vcpu)->rflags; It assumes rflags was decached from the VMCS before. Probably it is true, but…