On 05/17/2014 01:44 PM, Roman Bogorodskiy wrote: > In a number of places in the bhyve driver, virObjectUnlock() > is called with an arg without check if the arg is non-NULL, which > could result in passing NULL value and a warning like: > > virObjectUnlock:340 : Object 0x0 ((unknown)) is not a virObjectLockable instance Doesn't this instead argue that we should fix virObjectUnlock to gracefully handle a NULL parameter, rather than making every caller uglier? -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list