summaryrefslogtreecommitdiffstats
path: root/drivers/lguest/interrupts_and_traps.c
diff options
context:
space:
mode:
authorMatias Zabaljauregui <zabaljauregui@gmail.com>2009-04-08 17:58:39 -0300
committerRusty Russell <rusty@rustcorp.com.au>2009-04-19 23:14:00 +0930
commit88df781afb788fa588dbf2e77f205214022a8893 (patch)
treeb73e2b470a959e60fb5332737c1fca04bb629ba7 /drivers/lguest/interrupts_and_traps.c
parentff54250a0ebab7f90a5f848a0ba63f999830c872 (diff)
downloadop-kernel-dev-88df781afb788fa588dbf2e77f205214022a8893.zip
op-kernel-dev-88df781afb788fa588dbf2e77f205214022a8893.tar.gz
lguest: fix crash on vmlinux images
Typical message: 'lguest: unhandled trap 6 at 0x418726 (0x0)' vmlinux guests were broken by 4cd8b5e2a159f18a1507f1187b44a1acbfa6341b 'lguest: use KVM hypercalls', which rewrites guest text from kvm hypercalls to trap 31. The Launcher mmaps the kernel image. The Guest executes and immediately faults in the first text page (read-only). Then it hits a hypercall, and we rewrite that hypercall, causing a copy-on-write. But the Guest pagetables still refer to the old page: we fault again, but as Host we see the hypercall already rewritten, and pass the fault back to the Guest. The Guest hasn't set up an IDT yet, so we kill it. This doesn't happen with bzImages: they unpack themselves and so the text pages are already read-write. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Tested-by: Patrick McHardy <kaber@trash.net>
Diffstat (limited to 'drivers/lguest/interrupts_and_traps.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud