Eric Blake cfe087a211 blockjob: avoid compiler uncertainty in info sizing ... We have a policy of avoiding enum types in structs in our public API, because it is possible for a client to choose compiler options that can change the in-memory ABI of that struct based on whether the enum value occupies an int or a minimal size. But we missed this for virDomainBlockJobInfo. We got lucky on little-endian machines - if the enum fits minimal size (a char), we still end up padding to the next long before the next field; but on big-endian, a client interpreting the enum as a char would always see 0 when the server supplies contents as an int. * include/libvirt/libvirt.h.in (virDomainBlockJobInfo): Enforce particular sizing. Signed-off-by: Eric Blake <eblake@redhat.com>		2014-06-16 11:13:35 -06:00
..
libvirt	blockjob: avoid compiler uncertainty in info sizing	2014-06-16 11:13:35 -06:00
Makefile.am	maint: use LGPL correctly	2013-05-20 14:03:48 -06:00