Re: [libvirt] [PATCH] [Changelog]:If there is a process with a client which registers event callbacks, and it calls libvirt's API which uses the same virConnectPtr in that callback function. When this

Not sure you followed the exact meaning from the hacking page - that's an awfully long commit message string. It should be a single line of up to about 70 chars with "details" in the commit message itself somewhat like the original patch, e.g.: "remote: Fix use after free reference for

[libvirt] [PATCH] [Changelog]:If there is a process with a client which registers event callbacks, and it calls libvirt's API which uses the same virConnectPtr in that callback function. When this pro

#0 0x7fda223d66d8 in virClassIsDerivedFrom (klass=0xdeadbeef, parent=0x7fda24c81b40) at util/virobject.c:169 #1 0x7fda223d6a1e in virObjectIsClass (anyobj=anyobj@entry=0x7fd9e575b400, klass=) at util/virobject.c:365 #2 0x7fda223d6a44 in virObjectLock