diff options
| author | Paolo Bonzini | 2014-06-26 15:10:03 +0200 |
|---|---|---|
| committer | Paolo Bonzini | 2014-07-01 10:20:42 +0200 |
| commit | 352e8da743f26948cb12d0ee53c455f328f59bbe (patch) | |
| tree | 16c4c0990f625f55e1a69ca5b107d2a28db7b6b7 /include | |
| parent | memory: do not give a name to the internal exec.c regions (diff) | |
| download | qemu-352e8da743f26948cb12d0ee53c455f328f59bbe.tar.gz qemu-352e8da743f26948cb12d0ee53c455f328f59bbe.tar.xz qemu-352e8da743f26948cb12d0ee53c455f328f59bbe.zip | |
qdev: correctly send DEVICE_DELETED for recursively-deleted devices
When a device is unparented (i.e. made completely hidden from management)
we want to send a DEVICE_DELETED event only if the device actually was
realized. This avoids raising DEVICE_DELETED events when device_add
fails.
However, this does not work right for recursively-deleted
devices: the whole tree is _first_ unrealized, _then_ unparented.
Then device_unparent sees realized==false and fails to trigger
the event. The solution is simply to move have_realized into
the DeviceState struct. If device_add fails, we never set the
new field to true and DEVICE_DELETED is not sent.
Fixes qemu-iotests testcase 067 (broken by commit 5942a19, though that
commit in turn fixed a possible segfault in the same test).
Reported-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'include')
| -rw-r--r-- | include/hw/qdev-core.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/hw/qdev-core.h b/include/hw/qdev-core.h index 9221cfc879..0799ff29b0 100644 --- a/include/hw/qdev-core.h +++ b/include/hw/qdev-core.h @@ -156,6 +156,7 @@ struct DeviceState { const char *id; bool realized; + bool pending_deleted_event; QemuOpts *opts; int hotplugged; BusState *parent_bus; |