On Tue, Oct 08, 2013 at 07:02:44PM +0200, Paolo Bonzini wrote:
> Il 20/09/2013 16:57, Paolo Bonzini ha scritto:
> > This series fixes hot-unplug of virtio devices, which can crash due to
> > dangling pointer accesses.
> >
> > The current implementation supports guest-initiated hot-unplug via the
>
Il 20/09/2013 16:57, Paolo Bonzini ha scritto:
> This series fixes hot-unplug of virtio devices, which can crash due to
> dangling pointer accesses.
>
> The current implementation supports guest-initiated hot-unplug via the
> virtio_bus_destroy_device function, but not hot-unplugging the virtio
>
Il 22/09/2013 10:08, Paolo Bonzini ha scritto:
> Il 21/09/2013 21:17, Michael S. Tsirkin ha scritto:
>> On Fri, Sep 20, 2013 at 04:57:49PM +0200, Paolo Bonzini wrote:
>>> This series fixes hot-unplug of virtio devices, which can crash due to
>>> dangling pointer accesses.
>>
>> Could you please des
Il 21/09/2013 21:17, Michael S. Tsirkin ha scritto:
> On Fri, Sep 20, 2013 at 04:57:49PM +0200, Paolo Bonzini wrote:
>> This series fixes hot-unplug of virtio devices, which can crash due to
>> dangling pointer accesses.
>
> Could you please describe the sequence of steps that makes
> qemu crash?
On Fri, Sep 20, 2013 at 04:57:49PM +0200, Paolo Bonzini wrote:
> This series fixes hot-unplug of virtio devices, which can crash due to
> dangling pointer accesses.
Could you please describe the sequence of steps that makes
qemu crash?
> The current implementation supports guest-initiated hot-unp
This series fixes hot-unplug of virtio devices, which can crash due to
dangling pointer accesses.
The current implementation supports guest-initiated hot-unplug via the
virtio_bus_destroy_device function, but not hot-unplugging the virtio
device by virtue of unplugging its parent container device.
