mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Quan Xu <quan.xu0@gmail.com>
To: Wanpeng Li <kernellwp@gmail.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Wanpeng Li" <wanpeng.li@hotmail.com>,
	"Jim Mattson" <jmattson@google.com>
Subject: Re: [PATCH v3] KVM: X86: Fix load RFLAGS w/o the fixed bit
Date: Thu, 7 Dec 2017 17:24:28 +0800	[thread overview]
Message-ID: <86fcd0c7-c129-8567-c204-fbe7d8ea8f91@gmail.com> (raw)
In-Reply-To: <1512635408-11645-1-git-send-email-wanpeng.li@hotmail.com>



On 2017/12/07 16:30, Wanpeng Li wrote:
> From: Wanpeng Li <wanpeng.li@hotmail.com>
>
>   *** Guest State ***
>   CR0: actual=0x0000000000000030, shadow=0x0000000060000010, gh_mask=fffffffffffffff7
>   CR4: actual=0x0000000000002050, shadow=0x0000000000000000, gh_mask=ffffffffffffe871
>   CR3 = 0x00000000fffbc000
>   RSP = 0x0000000000000000  RIP = 0x0000000000000000
>   RFLAGS=0x00000000         DR7 = 0x0000000000000400
>          ^^^^^^^^^^
>
> The failed vmentry is triggered by the following testcase when ept=Y:
>
>      #include <unistd.h>
>      #include <sys/syscall.h>
>      #include <string.h>
>      #include <stdint.h>
>      #include <linux/kvm.h>
>      #include <fcntl.h>
>      #include <sys/ioctl.h>
>      
>      long r[5];
>      int main()
>      {
>      	r[2] = open("/dev/kvm", O_RDONLY);
>      	r[3] = ioctl(r[2], KVM_CREATE_VM, 0);
>      	r[4] = ioctl(r[3], KVM_CREATE_VCPU, 7);
>      	struct kvm_regs regs = {
>      		.rflags = 0,
>      	};
>      	ioctl(r[4], KVM_SET_REGS, &regs);
>      	ioctl(r[4], KVM_RUN, 0);
>      }
>
> X86 RFLAGS bit 1 is fixed set, userspace can simply clearing bit 1
> of RFLAGS with KVM_SET_REGS ioctl which results in vmentry fails.
> This patch fixes it by oring X86_EFLAGS_FIXED during ioctl.
>
> Suggested-by: Jim Mattson <jmattson@google.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Cc: Jim Mattson <jmattson@google.com>
> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com>
   Reviewed-by: Quan Xu <quan.xu0@gmail.com>

      reply	other threads:[~2017-12-07  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  8:30 Wanpeng Li
2017-12-07  9:24 ` Quan Xu [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=86fcd0c7-c129-8567-c204-fbe7d8ea8f91@gmail.com \
    --to=quan.xu0@gmail.com \
    --cc=jmattson@google.com \
    --cc=kernellwp@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=wanpeng.li@hotmail.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®