linux-kernel - Re: [PATCH] KVM: x86: fix eflags state following processor init/reset

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BLU436-SMTP850DA2036365FAA44972FB80210@phx.gbl>
Date:	Wed, 28 Oct 2015 11:24:15 +0800
From:	Wanpeng Li <wanpeng.li@...mail.com>
To:	Paolo Bonzini <pbonzini@...hat.com>
CC:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] KVM: x86: fix eflags state following processor init/reset

Ping, :-)
On 10/21/15 2:28 PM, Wanpeng Li wrote:
> Reference SDM 3.4.3:
>
> Following initialization of the processor (either by asserting the
> RESET pin or the INIT pin), the state of the EFLAGS register is
> 00000002H.
>
> However, the eflags fixed bit is not set and other bits are also not
> cleared during the init/reset in kvm.
>
> This patch fix it by set eflags register to 00000002H following
> initialization of the processor.
>
> Signed-off-by: Wanpeng Li <wanpeng.li@...mail.com>
> ---
>   arch/x86/kvm/vmx.c | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index b680c2e..326f6ea 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -4935,6 +4935,7 @@ static void vmx_vcpu_reset(struct kvm_vcpu *vcpu, bool init_event)
>   	vmx_set_efer(vcpu, 0);
>   	vmx_fpu_activate(vcpu);
>   	update_exception_bitmap(vcpu);
> +	vmx_set_rflags(vcpu, X86_EFLAGS_FIXED);
>   
>   	vpid_sync_context(vmx->vpid);
>   }

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/