All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] kvm segfault in iov_to_buf / virtio_scsi_parse_req
Date: Sat, 18 Oct 2014 21:51:43 +0200	[thread overview]
Message-ID: <5442C4CF.5050404@profihost.ag> (raw)

Hi,

while migrating a bunch of VMs i saw multiple times segaults with qemu 
2.1.2.

Is this a known bug?

Full backtrace:
Program terminated with signal 11, Segmentation fault.
#0  0x00007ff9c73bca90 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x00007ff9c73bca90 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ff9cde46b8e in iov_to_buf (iov=0x7ff9b805c0b0, iov_cnt=1, 
offset=0, buf=0x7ff9b8060118, bytes=51) at util/iov.c:49
#2  0x00007ff9cdacdc56 in virtio_scsi_parse_req (req=0x7ff9b8054090, 
req_size=51, resp_size=108)
     at qemu-kvm/hw/scsi/virtio-scsi.c:140
#3  0x00007ff9cdace060 in virtio_scsi_load_request (f=0x7ff9b803b620, 
sreq=0x7ff9b8089550)
     at qemu-kvm/hw/scsi/virtio-scsi.c:215
#4  0x00007ff9cdcf5737 in get_scsi_requests (f=0x7ff9b803b620, 
pv=0x7ff9cfe4a440, size=0) at hw/scsi/scsi-bus.c:1875
#5  0x00007ff9cdb76e0c in vmstate_load_state (f=0x7ff9b803b620, 
vmsd=0x7ff9ce24cac0, opaque=0x7ff9cfe4a440, version_id=1)
     at vmstate.c:105
#6  0x00007ff9cdb76de8 in vmstate_load_state (f=0x7ff9b803b620, 
vmsd=0x7ff9ce24c500, opaque=0x7ff9cfe4a440, version_id=1)
     at vmstate.c:102
#7  0x00007ff9cda935b6 in vmstate_load (f=0x7ff9b803b620, 
se=0x7ff9cfe95570, version_id=1)
     at qemu-kvm/savevm.c:572
#8  0x00007ff9cda94652 in qemu_loadvm_state (f=0x7ff9b803b620)
     at qemu-kvm/savevm.c:951
#9  0x00007ff9cdb748bd in process_incoming_migration_co 
(opaque=0x7ff9b803b620) at migration.c:97
#10 0x00007ff9cdddb433 in coroutine_trampoline (i0=-1207852976, 
i1=32761) at coroutine-ucontext.c:118
#11 0x00007ff9c72dbd10 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#12 0x00007fff5e55a830 in ?? ()
#13 0x0000000000000000 in ?? ()

Stefan

                 reply	other threads:[~2014-10-18 19:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5442C4CF.5050404@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=qemu-devel@nongnu.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 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.