All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Nadav Amit <namit@cs.technion.ac.il>, pbonzini@redhat.com
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 2/8] KVM: x86: pop sreg accesses only 2 bytes
Date: Thu, 25 Dec 2014 17:10:53 +0800	[thread overview]
Message-ID: <549BD49D.3060200@intel.com> (raw)
In-Reply-To: <1419468743-23732-3-git-send-email-namit@cs.technion.ac.il>

On 2014/12/25 8:52, Nadav Amit wrote:
> Although pop sreg updates RSP according to the operand size, only 2 bytes are
> read.  The current behavior may result in incorrect #GP or #PF exceptions.
>
> Signed-off-by: Nadav Amit <namit@cs.technion.ac.il>
> ---
>   arch/x86/kvm/emulate.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> index e5a84be..702da5e 100644
> --- a/arch/x86/kvm/emulate.c
> +++ b/arch/x86/kvm/emulate.c
> @@ -1830,12 +1830,14 @@ static int em_pop_sreg(struct x86_emulate_ctxt *ctxt)
>   	unsigned long selector;
>   	int rc;
>

Looks we just should do similar thing to em_push_sreg(),

         unsigned long selector;
         int rc;

+       if (ctxt->op_bytes == 4) {
+               rsp_increment(ctxt, -2);
+               ctxt->op_bytes = 2;
+       }
         rc = emulate_pop(ctxt, &selector, ctxt->op_bytes);
         if (rc != X86EMUL_CONTINUE)
                 return rc;

Right?

Thanks
Tiejun

> -	rc = emulate_pop(ctxt, &selector, ctxt->op_bytes);
> +	rc = emulate_pop(ctxt, &selector, 2);
>   	if (rc != X86EMUL_CONTINUE)
>   		return rc;
>
>   	if (ctxt->modrm_reg == VCPU_SREG_SS)
>   		ctxt->interruptibility = KVM_X86_SHADOW_INT_MOV_SS;
> +	if (ctxt->op_bytes > 2)
> +		rsp_increment(ctxt, ctxt->op_bytes - 2);
>
>   	rc = load_segment_descriptor(ctxt, (u16)selector, seg);
>   	return rc;
>

  reply	other threads:[~2014-12-25  9:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-25  0:52 [PATCH 0/8] KVM: x86: Emulator fixes Nadav Amit
2014-12-25  0:52 ` [PATCH 1/8] KVM: x86: #PF error-code on R/W operations is wrong Nadav Amit
2014-12-26  7:25   ` Wu, Feng
2014-12-27 19:55     ` Nadav Amit
2014-12-25  0:52 ` [PATCH 2/8] KVM: x86: pop sreg accesses only 2 bytes Nadav Amit
2014-12-25  9:10   ` Chen, Tiejun [this message]
2014-12-25  9:55     ` Nadav Amit
2014-12-26  1:54       ` Chen, Tiejun
2014-12-26  7:25       ` Wu, Feng
2014-12-27 20:05         ` Nadav Amit
2014-12-25  0:52 ` [PATCH 3/8] KVM: x86: fnstcw and fnstsw may cause spurious exception Nadav Amit
2014-12-25  0:52 ` [PATCH 4/8] KVM: x86: JMP/CALL using call- or task-gate causes exception Nadav Amit
2014-12-25  0:52 ` [PATCH 5/8] KVM: x86: em_call_far should return failure result Nadav Amit
2014-12-25  0:52 ` [PATCH 6/8] KVM: x86: POP [ESP] is not emulated correctly Nadav Amit
2014-12-25  0:52 ` [PATCH 7/8] KVM: x86: Do not set access bit on accessed segments Nadav Amit
2014-12-25  0:52 ` [PATCH 8/8] KVM: x86: Access to LDT/GDT that wraparound is incorrect Nadav Amit
2014-12-27 22:24 ` [PATCH 0/8] KVM: x86: Emulator fixes Paolo Bonzini
2015-01-08 10:42 ` Paolo Bonzini

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=549BD49D.3060200@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=namit@cs.technion.ac.il \
    --cc=pbonzini@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 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.