mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-08-28 11:31:16 +00:00
Expose virCapabilitiesFreeGuest
Guests are handled in callers, but if something goes wrong (when it cannot be added to virCapabilities, for example), there's no way for them to free it properly. Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
This commit is contained in:
parent
272d78a5ef
commit
e8e9a7e9f7
@ -148,7 +148,7 @@ virCapabilitiesFreeGuestFeature(virCapsGuestFeaturePtr feature)
|
||||
VIR_FREE(feature);
|
||||
}
|
||||
|
||||
static void
|
||||
void
|
||||
virCapabilitiesFreeGuest(virCapsGuestPtr guest)
|
||||
{
|
||||
size_t i;
|
||||
|
@ -248,6 +248,9 @@ void
|
||||
virCapabilitiesFreeMachines(virCapsGuestMachinePtr *machines,
|
||||
int nmachines);
|
||||
|
||||
void
|
||||
virCapabilitiesFreeGuest(virCapsGuestPtr guest);
|
||||
|
||||
virCapsGuestPtr
|
||||
virCapabilitiesAddGuest(virCapsPtr caps,
|
||||
int ostype,
|
||||
|
@ -53,6 +53,7 @@ virCapabilitiesAllocMachines;
|
||||
virCapabilitiesClearHostNUMACellCPUTopology;
|
||||
virCapabilitiesDomainDataLookup;
|
||||
virCapabilitiesFormatXML;
|
||||
virCapabilitiesFreeGuest;
|
||||
virCapabilitiesFreeMachines;
|
||||
virCapabilitiesFreeNUMAInfo;
|
||||
virCapabilitiesGetCpusForNodemask;
|
||||
|
Loading…
Reference in New Issue
Block a user