提交 c9791620 编写于 作者: D Daniel P. Berrange 提交者: Cole Robinson

Remove pointless virLXCProcessMonitorDestroy method

Asynchronously setting priv->mon to NULL was pointless,
just remove the destroy callback entirely.
Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
(cherry picked from commit dd037176)
上级 df2b4be5
......@@ -554,20 +554,6 @@ cleanup:
}
static void virLXCProcessMonitorDestroy(virLXCMonitorPtr mon,
virDomainObjPtr vm)
{
virLXCDomainObjPrivatePtr priv;
virDomainObjLock(vm);
priv = vm->privateData;
if (priv->monitor == mon)
priv->monitor = NULL;
if (virObjectUnref(vm))
virDomainObjUnlock(vm);
}
extern virLXCDriverPtr lxc_driver;
static void virLXCProcessMonitorEOFNotify(virLXCMonitorPtr mon ATTRIBUTE_UNUSED,
virDomainObjPtr vm)
......@@ -649,7 +635,6 @@ static void virLXCProcessMonitorExitNotify(virLXCMonitorPtr mon ATTRIBUTE_UNUSED
static virLXCMonitorCallbacks monitorCallbacks = {
.eofNotify = virLXCProcessMonitorEOFNotify,
.destroy = virLXCProcessMonitorDestroy,
.exitNotify = virLXCProcessMonitorExitNotify,
};
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册