On 08/27/2014 10:54 PM, John Ferlan wrote: > I almost didn't want to do this due to the sheer volume, but figured > at the very least the bulk of these are resource leaks found by the > much pickier new coverity scanner. > > After this there are "only" 70 issues found... > > John Ferlan (19): > libxl_migration: Resolve Coverity NULL_RETURNS I still don't know how to answer this one. ACK to the rest, see my reply to 3/19 for a minor tweak. Jan > daemon: Resolve Coverity NEGATIVE_RETURNS > domain_conf: Resolve Coverity RESOURCE_LEAK > cpu_x86: Resolve Coverity RESOURCE_LEAK > qemu_command: Resolve Coverity RESOURCE_LEAK > qemu_agent: Resolve Coverity RESOURCE_LEAK > libxl_domain: Resolve Coverity RESOURCE_LEAK > qemu_capabilities: Resolve Coverity RESOURCE_LEAK > network_conf: Resolve Coverity RESOURCE_LEAK > virsh-network: Resolve Coverity RESOURCE_LEAK > bridge_driver: Resolve Coverity RESOURCE_LEAK > libxl_migration: Resolve Coverity RESOURCE_LEAK > phyp_driver: Resolve Coverity RESOURCE_LEAK > qemu_driver: Resolve Coverity RESOURCE_LEAK > storage_conf: Resolve Coverity RESOURCE_LEAK > qemu_monitor: Resolve Coverity NESTING_INDENT_MISMATCH > domain_conf: Resolve Coverity DEADCODE > qemu_driver: Resolve Coverity DEADCODE > qemu_command: Resolve Coverity DEADCODE
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list