Make sure object is valid when destructor is called.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
qom/object.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/qom/object.c b/qom/object.c
index 3d638ff..a0e3cbe 100644
--- a/qom/object.c
+++ b/qom/object.c
@@
Il 21/03/2013 13:07, Michael S. Tsirkin ha scritto:
Make sure object is valid when destructor is called.
Make sure the object still has a canonical path while the unparent
callback is running.
Otherwise, the series looks good.
Paolo
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
On Thu, Mar 21, 2013 at 01:25:50PM +0100, Paolo Bonzini wrote:
Il 21/03/2013 13:07, Michael S. Tsirkin ha scritto:
Make sure object is valid when destructor is called.
Make sure the object still has a canonical path while the unparent
callback is running.
Otherwise, the series looks
Il 21/03/2013 13:30, Michael S. Tsirkin ha scritto:
On Thu, Mar 21, 2013 at 01:25:50PM +0100, Paolo Bonzini wrote:
Il 21/03/2013 13:07, Michael S. Tsirkin ha scritto:
Make sure object is valid when destructor is called.
Make sure the object still has a canonical path while the unparent
