From: Avi Kivity <avi@qumranet.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] guest crash on 2.6.20-rc4
Date: Tue, 09 Jan 2007 23:26:48 +0200 [thread overview]
Message-ID: <45A40898.4040307@qumranet.com> (raw)
In-Reply-To: <ada4pr1mqz2.fsf@cisco.com>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
Roland Dreier wrote:
> I'm running a 64-bit Fedora 6 install as a guest on a host running
> 2.6.20-rc4 with the kvm-10 userspace release. The CPU is a Xeon 5160
> and I have 6 GB of RAM. The guest is given 512 MB of memory. I left
> the guest idle overnight, and the makewhatis cron job seems to have
> triggered this:
>
> Unable to handle kernel paging request at ffff81000ba04000 RIP:
> [<ffffffff8025f402>] clear_page+0x16/0x44
>
I've managed to reproduce a bug with similar characteristics: a write
fault into a present, writable kernel page. The attached patch should
fix it.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
[-- Attachment #2: spurious-page-fault.patch --]
[-- Type: text/x-patch, Size: 386 bytes --]
Index: b/drivers/kvm/paging_tmpl.h
===================================================================
--- a/drivers/kvm/paging_tmpl.h (revision 4270)
+++ b/drivers/kvm/paging_tmpl.h (working copy)
@@ -274,7 +274,7 @@
struct kvm_mmu_page *page;
if (is_writeble_pte(*shadow_ent))
- return 0;
+ return 1;
writable_shadow = *shadow_ent & PT_SHADOW_WRITABLE_MASK;
if (user) {
next prev parent reply other threads:[~2007-01-09 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 16:18 guest crash on 2.6.20-rc4 Roland Dreier
2007-01-09 8:53 ` [kvm-devel] " Avi Kivity
2007-01-09 8:53 ` Avi Kivity
2007-01-09 21:26 ` Avi Kivity [this message]
2007-01-10 18:31 ` [kvm-devel] " Roland Dreier
2007-01-10 21:33 ` Roland Dreier
2007-01-10 21:33 ` Roland Dreier
2007-01-11 8:06 ` [kvm-devel] " Avi Kivity
2007-01-11 8:06 ` 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=45A40898.4040307@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.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.