libvirt/src
Shi Lei f9a59e051c util: netdevip: Fix a memleak in virNetDevIPRouteAdd
@resp is allocated by virNetlinkCommand and the caller is responsible
for freeing the buffer. Since we already converted this module to use
VIR_AUTO{FREE,PTR} macros, let's resolve the problem by using them.

Signed-off-by: Shi Lei <shi_lei@massclouds.com>
Reviewed-by: Erik Skultety <eskultet@redhat.com>
2018-09-07 13:33:57 +02:00
..
access
admin
bhyve
conf nwfilter: Check for filter presence before open connect during teardown 2018-09-06 18:38:22 -04:00
cpu
cpu_map
esx
hyperv
interface
keycodemapdb@16e5b07876
libxl
locking virLockManagerLockDaemonAddResource: Switch to cleanup label rather than error 2018-09-05 10:59:32 +02:00
logging
lxc
network
node_device
nwfilter nwfilter: Disallow binding creation in session mode 2018-09-06 18:38:06 -04:00
openvz
phyp
qemu qemuDomainNamespaceTeardownHostdev: Drop useless check 2018-09-07 07:11:16 +02:00
remote
rpc
secret
security security_dac: Fix const correctness 2018-09-07 09:57:39 +02:00
storage storage_driver: Release pool object lock for some long running jobs 2018-09-04 10:11:40 +02:00
test virstorageobj: Check for duplicates from virStoragePoolObjAssignDef 2018-09-04 10:11:40 +02:00
uml
util util: netdevip: Fix a memleak in virNetDevIPRouteAdd 2018-09-07 13:33:57 +02:00
vbox
vmware
vmx
vz
xenapi
xenconfig
admin_protocol-structs
check-aclperms.pl
check-aclrules.pl
check-driverimpls.pl
check-drivername.pl
check-symfile.pl
check-symsorting.pl
datatypes.c
datatypes.h
driver-hypervisor.h
driver-interface.h
driver-network.h
driver-nodedev.h
driver-nwfilter.h
driver-secret.h Introduce secret lifecycle event APIs 2017-01-09 15:53:48 +00:00
driver-state.h
driver-storage.h
driver-stream.h
driver.c
driver.h
dtrace2systemtap.pl
internal.h
libvirt_admin_private.syms admin: Introduce virAdmConnectSetLoggingFilters 2016-12-15 10:36:23 +01:00
libvirt_admin_public.syms
libvirt_atomic.syms
libvirt_driver_modules.syms
libvirt_esx.syms
libvirt_internal.h
libvirt_libssh2.syms
libvirt_libssh.syms
libvirt_linux.syms
libvirt_lxc.syms
libvirt_openvz.syms
libvirt_private.syms conf: Rename virDomainPCIAddressAsString() 2018-09-05 15:51:40 +02:00
libvirt_probes.d Forget last daemon/ dir artefacts 2018-07-27 15:44:38 +02:00
libvirt_public.syms
libvirt_qemu_probes.d
libvirt_qemu.syms
libvirt_remote.syms
libvirt_sasl.syms
libvirt_vmware.syms
libvirt_vmx.syms
libvirt_xenconfig.syms
libvirt-admin.c
libvirt-admin.conf
libvirt-domain-snapshot.c
libvirt-domain.c docs: Typo fix in virDomainGetJobStats 2018-09-05 14:34:33 -05:00
libvirt-host.c
libvirt-interface.c
libvirt-lxc.c
libvirt-lxc.pc.in
libvirt-network.c
libvirt-nodedev.c
libvirt-nwfilter.c
libvirt-qemu.c
libvirt-qemu.pc.in
libvirt-secret.c
libvirt-storage.c
libvirt-stream.c
libvirt.c
libvirt.conf
libvirt.pc.in
lock_protocol-structs
lxc_monitor_protocol-structs
lxc_protocol-structs
Makefile.am
qemu_protocol-structs
README
remote_protocol-structs
virkeepaliveprotocol-structs build: Properly generate and check virkeepaliveprotocol-structs 2011-11-24 14:44:04 +01:00
virnetprotocol-structs

       libvirt library code README
       ===========================

The directory provides the bulk of the libvirt codebase. Everything
except for the libvirtd daemon and client tools. The build uses a
large number of libtool convenience libraries - one for each child
directory, and then links them together for the final libvirt.so,
although some bits get linked directly to libvirtd daemon instead.

The files directly in this directory are supporting the public API
entry points & data structures.

There are two core shared modules to be aware of:

 * util/  - a collection of shared APIs that can be used by any
            code. This directory is always in the include path
            for all things built

 * conf/  - APIs for parsing / manipulating all the official XML
            files used by the public API. This directory is only
            in the include path for driver implementation modules

 * vmx/   - VMware VMX config handling (used by esx/ and vmware/)


Then there are the hypervisor implementations:

 * bhyve         - bhyve - The BSD Hypervisor
 * esx/          - VMware ESX and GSX support using vSphere API over SOAP
 * hyperv/       - Microsoft Hyper-V support using WinRM
 * lxc/          - Linux Native Containers
 * openvz/       - OpenVZ containers using cli tools
 * phyp/         - IBM Power Hypervisor using CLI tools over SSH
 * qemu/         - QEMU / KVM using qemu CLI/monitor
 * remote/       - Generic libvirt native RPC client
 * test/         - A "mock" driver for testing
 * uml/          - User Mode Linux
 * vbox/         - Virtual Box using native API
 * vmware/       - VMware Workstation and Player using the vmrun tool
 * xen/          - Xen using hypercalls, XenD SEXPR & XenStore
 * xenapi/       - Xen using libxenserver


Finally some secondary drivers that are shared for several HVs.
Currently these are used by LXC, OpenVZ, QEMU, UML and Xen drivers.
The ESX, Hyper-V, Power Hypervisor, Remote, Test & VirtualBox drivers all
implement the secondary drivers directly

 * cpu/          - CPU feature management
 * interface/    - Host network interface management
 * network/      - Virtual NAT networking
 * nwfilter/     - Network traffic filtering rules
 * node_device/  - Host device enumeration
 * secret/       - Secret management
 * security/     - Mandatory access control drivers
 * storage/      - Storage management drivers


Since both the hypervisor and secondary drivers can be built as
dlopen()able modules, it is *FORBIDDEN* to have build dependencies
between these directories. Drivers are only allowed to depend on
the public API, and the internal APIs in the util/ and conf/
directories