On Fri, 2017-09-01 at 13:49 +0100, Daniel P. Berrange wrote: > Although not previously explicitly documented, the expectation for > the libvirt event loop is that an implementation is registered early > in application startup, before calling any libvirt APIs and then > run forever after. Replacing a previously registered event loop is > not safe & subject to races even if virConnectClose has been called > on open handles, due to delayed deregistration of callbacks during > conenction close. > > Signed-off-by: Daniel P. Berrange <berrange@xxxxxxxxxx> > --- > src/util/virevent.c | 13 +++++++++++++ > 1 file changed, 13 insertions(+) Reviewed-by: Andrea Bolognani <abologna@xxxxxxxxxx> -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
