From: Nadav Amit <nadav.amit@gmail.com>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Nadav Amit <namit@cs.technion.ac.il>,
Paolo Bonzini <pbonzini@redhat.com>, X86 ML <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Testcases for "eip canonical" kvm fixes?
Date: Wed, 11 Mar 2015 15:03:59 +0200 [thread overview]
Message-ID: <F5A20660-7FDF-4A66-BA45-95A709E669AD@gmail.com> (raw)
In-Reply-To: <CAK1hOcNXVFAWdCLAVintr_XUAVP5dT5C+g4t4DJty7kqGYq4tA@mail.gmail.com>
Automatic testings. I am working on a research paper regarding it, so I’ll
publish the details (hopefully) in the near future.
Nadav
Denys Vlasenko <vda.linux@googlemail.com> wrote:
> Hi,
>
> I wonder how did you trigger the bug for your following fix?
>
>
> commit 234f3ce485d54017f15cf5e0699cff4100121601
> Author: Nadav Amit <namit@cs.technion.ac.il>
> Date: Thu Sep 18 22:39:38 2014 +0300
>
> KVM: x86: Emulator fixes for eip canonical checks on near branches
>
> Before changing rip (during jmp, call, ret, etc.) the target
> should be asserted
> to be canonical one, as real CPUs do. During sysret, both target
> rsp and rip
> should be canonical. If any of these values is noncanonical, a #GP exception
> should occur. The exception to this rule are syscall and sysenter
> instructions
> in which the assigned rip is checked during the assignment to the relevant
> MSRs.
>
> This patch fixes the emulator to behave as real CPUs do for near branches.
> Far branches are handled by the next patch.
>
>
> Non-canonical addresses result in #GP, but KVM doesn't
> intercept guest #GP, according to code below:
>
> static void update_exception_bitmap(struct kvm_vcpu *vcpu)
> {
> u32 eb;
>
> eb = (1u << PF_VECTOR) | (1u << UD_VECTOR) | (1u << MC_VECTOR) |
> (1u << NM_VECTOR) | (1u << DB_VECTOR);
> if ((vcpu->guest_debug &
> (KVM_GUESTDBG_ENABLE | KVM_GUESTDBG_USE_SW_BP)) ==
> (KVM_GUESTDBG_ENABLE | KVM_GUESTDBG_USE_SW_BP))
> eb |= 1u << BP_VECTOR;
> if (to_vmx(vcpu)->rmode.vm86_active)
> eb = ~0;
> if (enable_ept)
> eb &= ~(1u << PF_VECTOR); /* bypass_guest_pf = 0 */
> if (vcpu->fpu_active)
> eb &= ~(1u << NM_VECTOR);
>
> /* When we are running a nested L2 guest and L1 specified for it a
> * certain exception bitmap, we must trap the same exceptions and pass
> * them to L1. When running L2, we will only handle the exceptions
> * specified above if L1 did not want them.
> */
> if (is_guest_mode(vcpu))
> eb |= get_vmcs12(vcpu)->exception_bitmap;
>
> vmcs_write32(EXCEPTION_BITMAP, eb);
> }
>
>
> That what seems to be happening to me when I try to reproduce
> the bug on unpatched kernel: CPU simply emulates #GP, and
> everything works as it should.
>
> In particular:
> I'm trying "RET far" with noncanonical address on stack (and valid CS).
> I expect that buggy behavior would be that #GP happens
> after "RET far". Instead, #GP happens _on_ "RET far" insn.
>
> --
> vda
next prev parent reply other threads:[~2015-03-11 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 18:37 Denys Vlasenko
2015-03-11 13:03 ` Nadav Amit [this message]
2015-03-11 13:27 ` Denys Vlasenko
2015-03-11 13:50 ` Nadav Amit
2015-03-11 14:12 ` 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=F5A20660-7FDF-4A66-BA45-95A709E669AD@gmail.com \
--to=nadav.amit@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namit@cs.technion.ac.il \
--cc=pbonzini@redhat.com \
--cc=vda.linux@googlemail.com \
--cc=x86@kernel.org \
/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®