From: Avi Kivity <avi@redhat.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: 2.6.38.1 general protection fault
Date: Sun, 27 Mar 2011 11:42:35 +0200 [thread overview]
Message-ID: <4D8F068B.5030209@redhat.com> (raw)
In-Reply-To: <4D8DC307.7090400@wpkg.org>
On 03/26/2011 12:42 PM, Tomasz Chmielewski wrote:
> On 26.03.2011 10:15, Avi Kivity wrote:
> > On 03/25/2011 11:32 AM, Tomasz Chmielewski wrote:
> >> I got this on a 2.6.38.1 system which (I think) had some problem
> >> accessing guest image on a btrfs filesystem.
> >>
> >>
> >> general protection fault: 0000 [#1] SMP
>
> (...)
>
> > 0: 55 push %rbp
> > 1: 48 89 e5 mov %rsp,%rbp
> > 4: 41 55 push %r13
> > 6: 41 54 push %r12
> > 8: 53 push %rbx
> > 9: 48 83 ec 08 sub $0x8,%rsp
> > d: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1)
> > 12: 45 31 e4 xor %r12d,%r12d
> > 15: 48 89 fb mov %rdi,%rbx
> > 18: 49 89 f5 mov %rsi,%r13
> > 1b: eb 1d jmp 0x3a
> > 1d: 0f 1f 00 nopl (%rax)
> > 20: f6 06 01 testb $0x1,(%rsi)
> >
> >
> > Looks like the top 16 bits of %rsi are flipped.
> >
> > Also wierd to see a fork(). What's your qemu command line?
>
> /usr/bin/kvm -monitor unix:/var/run/qemu-server/113.mon,server,nowait -vnc unix:/var/run/qemu-server/113.vnc,password -pidfile /var/run/qemu-server/113.pid -daemonize -usbdevice tablet -name swcache -smp sockets=1,cores=1 -nodefaults -boot menu=on -vga cirrus -tdf -k de -drive file=/var/lib/vz/template/iso/systemrescuecd-x86-2.0.0.iso,if=ide,index=2,media=cdrom -drive file=/var/lib/vz/images/113/vm-113-disk-1.raw,if=scsi,index=0,cache=none,boot=on -m 1024 -netdev type=tap,id=vlan0d0,ifname=tap113i0d0,script=/var/lib/qemu-server/bridge-vlan,vhost=on -device virtio-net-pci,mac=DE:42:48:50:D8:69,netdev=vlan0d0 -netdev type=tap,id=vlan100d0,ifname=tap113i100d0,script=/var/lib/qemu-server/bridge-vlan,vhost=on -device virtio-net-pci,mac=72:D2:6E:8E:07:4D,netdev=vlan100d0
>
>
Okay, the fork came from the ,script=.
The issue with %rsi looks like a use-after-free, however
kvm_mmu_notifier_invalidate_range_start appears to be properly srcu
protected.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-03-27 9:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 9:32 2.6.38.1 general protection fault Tomasz Chmielewski
2011-03-26 9:15 ` Avi Kivity
2011-03-26 10:42 ` Tomasz Chmielewski
2011-03-27 9:42 ` Avi Kivity [this message]
2011-03-28 6:24 ` Tomasz Chmielewski
2011-03-28 9:19 ` Avi Kivity
2011-03-28 17:54 ` Andrea Arcangeli
2011-03-28 18:02 ` Avi Kivity
2011-03-28 20:04 ` Andrea Arcangeli
2011-03-28 20:14 ` Tomasz Chmielewski
2011-04-20 9:28 ` Thomas Treutner
2011-04-20 10:54 ` Tomasz Chmielewski
2011-03-29 13:34 ` Marcelo Tosatti
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=4D8F068B.5030209@redhat.com \
--to=avi@redhat.com \
--cc=aarcange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mangoo@wpkg.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;
as well as URLs for NNTP newsgroup(s).