On 12/2/18 1:19 PM, Richard W.M. Jones wrote:
I think attached is a better version of this patch. In particular it avoids setting the per-connection data until we're at the very end of the initialization function. Technically this is not part of the fix for the memory leak, but nevertheless this avoids any possible case where we might call crypto_close without a valid session along some error path.
Yes, I like this version better. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org _______________________________________________ Libguestfs mailing list [email protected] https://www.redhat.com/mailman/listinfo/libguestfs
