Re: [Qemu-devel] [PULL v2 for-2.0 13/24] dataplane: replace internal thread with IOThread

[Christian Borntraeger]

On 20/03/14 11:13, Stefan Hajnoczi wrote:
> On Mon, Mar 17, 2014 at 04:52:59PM +0100, Christian Borntraeger wrote:
>> This causes the following bug during managedsave of s390 with a guest that 
>> has multiple disks with dataplane.
>>
>> (gdb) bt
>> #0  object_deinit (type=0x0, obj=0x807e8750) at 
>> /home/cborntra/REPOS/qemu/qom/object.c:410
>> #1  object_finalize (data=0x807e8750) at 
>> /home/cborntra/REPOS/qemu/qom/object.c:424
>> #2  object_unref (obj=0x807e8750) at 
>> /home/cborntra/REPOS/qemu/qom/object.c:726
>> #3  0x000000008011da60 in object_property_del (obj=0x807e8d80, 
>> name=0x807e8d60 "virtio-blk", errp=<optimized out>) at 
>> /home/cborntra/REPOS/qemu/qom/object.c:783
>> #4  0x000000008011dc0e in object_property_del_child (errp=0x0, 
>> child=0x807e8750, obj=0x807e8d80) at 
>> /home/cborntra/REPOS/qemu/qom/object.c:386
>> #5  object_unparent (obj=0x807e8750) at 
>> /home/cborntra/REPOS/qemu/qom/object.c:403
>> #6  0x0000000080183898 in virtio_blk_data_plane_destroy (s=0x8088a750) at 
>> /home/cborntra/REPOS/qemu/hw/block/dataplane/virtio-blk.c:430
> 
> Are you able to reproduce this reliably?
> 
> 198fd05c357afff22f0b0e02639937519ed49b1f should have fixed it.

Yes, I agree this should fix it, but I cant no longer start my guest with > 1 
dataplane device, (see the 2nd
bug report) so I cant reproduce right now.