From: Avi Kivity <avi@redhat.com>
To: Benjamin Gilbert <bgilbert@cs.cmu.edu>
Cc: kvm@vger.kernel.org
Subject: Re: Kernel GPF in vmx_save_host_state()
Date: Mon, 23 Mar 2009 21:25:42 +0200 [thread overview]
Message-ID: <49C7E236.90902@redhat.com> (raw)
In-Reply-To: <49C7D7F4.7090204@cs.cmu.edu>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
Benjamin Gilbert wrote:
>>> vmx_set_msr: msr_index 0xc0000080 msr->index 0xc0000080 msr->data 0x100
>>
>> How did that get in there?!
>>
>> Please add a dump_stack() after that printk().
>
> Pid: 2381, comm: qemu-system-x86 Not tainted 2.6.28-686 #4
> Call Trace:
> [<f8cf2fdc>] vmx_set_msr+0x150/0x178 [kvm_intel]
> [<f8cf325a>] handle_wrmsr+0x71/0x9d [kvm_intel]
Duh, I noted this hole in a previous email.
Attached patch should fix.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
[-- Attachment #2: dont-allow-uninhibited-efer-access-on-i386.patch --]
[-- Type: text/x-patch, Size: 485 bytes --]
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 88ef094..da6461d 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -942,11 +942,11 @@ static int vmx_set_msr(struct kvm_vcpu *vcpu, u32 msr_index, u64 data)
int ret = 0;
switch (msr_index) {
-#ifdef CONFIG_X86_64
case MSR_EFER:
vmx_load_host_state(vmx);
ret = kvm_set_msr_common(vcpu, msr_index, data);
break;
+#ifdef CONFIG_X86_64
case MSR_FS_BASE:
vmcs_writel(GUEST_FS_BASE, data);
break;
next prev parent reply other threads:[~2009-03-23 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 23:24 Kernel GPF in vmx_save_host_state() Benjamin Gilbert
2009-03-18 8:55 ` Avi Kivity
2009-03-18 17:26 ` Benjamin Gilbert
2009-03-19 9:22 ` Avi Kivity
2009-03-19 21:00 ` Benjamin Gilbert
2009-03-22 9:08 ` Avi Kivity
2009-03-23 18:24 ` Benjamin Gilbert
2009-03-23 18:34 ` Avi Kivity
2009-03-23 18:41 ` Benjamin Gilbert
2009-03-23 19:25 ` Avi Kivity [this message]
2009-03-23 20:07 ` Benjamin Gilbert
2009-03-19 4:04 ` Amit Shah
2009-03-19 9:55 ` Avi Kivity
2009-03-19 10:16 ` Amit Shah
2009-03-19 10:30 ` Avi Kivity
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=49C7E236.90902@redhat.com \
--to=avi@redhat.com \
--cc=bgilbert@cs.cmu.edu \
--cc=kvm@vger.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