[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1793791] Re: Crash with nbd_reply_chunk_iter_receive:

From: Matthew Schumacher
Subject: [Qemu-devel] [Bug 1793791] Re: Crash with nbd_reply_chunk_iter_receive: Assertion `chunk->flags & NBD_REPLY_FLAG_DONE' failed
Date: Mon, 24 Sep 2018 20:23:33 -0000

>From the core:

structured = {magic = 1732535960, flags = 0, type = 0, handle =
94174913593865, length = 0}

You would think that would pass:

    chunk = &reply->structured;

    if (chunk->type == NBD_REPLY_TYPE_NONE) {
        /* NBD_REPLY_FLAG_DONE is already checked in nbd_co_receive_one_chunk */
        assert(chunk->flags & NBD_REPLY_FLAG_DONE);
        goto break_loop;


#define NBD_REPLY_TYPE_NONE          0

Perhaps this is a problem with my compiler.  (or maybe it's an ignorant guess) 
I'm using:

gcc version 5.5.0 (GCC)

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  Crash with nbd_reply_chunk_iter_receive: Assertion `chunk->flags &

Status in QEMU:

Bug description:
  Qemu version on both sides: 2.12.1
  Host A Linux: 4.9.76
  Host B Linux: 4.14.67

  While calling from Host A:
  virsh migrate virtualmachine qemu+ssh://hostB/system --live --undefinesource 
--persistent --verbose --copy-storage-all

  I get a qemu crash with:

  2018-09-21 16:12:23.073+0000: 14428: info : virObjectUnref:350 : 
OBJECT_UNREF: obj=0x7f922c03d990
  qemu-system-x86_64: block/nbd-client.c:606: nbd_reply_chunk_iter_receive: 
Assertion `chunk->flags & NBD_REPLY_FLAG_DONE' failed.
  2018-09-21 16:12:41.230+0000: shutting down, reason=crashed
  2018-09-21 16:12:52.900+0000: shutting down, reason=failed

  It doesn't do it every time, but most of the time.

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]