spapr: drop reference on child object during core realization
commit8e758dee663bfda2ccfe0076914bf49108055386
authorGreg Kurz <groug@kaod.org>
Wed, 29 Jun 2016 20:50:20 +0000 (29 22:50 +0200)
committerDavid Gibson <david@gibson.dropbear.id.au>
Fri, 1 Jul 2016 03:41:47 +0000 (1 13:41 +1000)
tree71550982af59d57c5bd757c79031755c348e5d23
parent470f2157877d49034d2ae0e755fbd4d059def164
spapr: drop reference on child object during core realization

When a core is being realized, we create a child object for each thread
of the core.

The child is first initialized with object_initialize() which sets its ref
count to 1, and then added to the core with object_property_add_child()
which bumps the ref count to 2.

When the core gets released, object_unparent() decreases the ref count to 1,
and we g_free() the object: we hence loose the reference on an unfinalized
object. This is likely to cause random crashes.

Let's drop the extra reference as soon as we don't need it, after the
thread is added to the core.

Signed-off-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
hw/ppc/spapr_cpu_core.c