diff options
author | Michael Roth <mdroth@linux.vnet.ibm.com> | 2014-09-18 15:36:40 -0500 |
---|---|---|
committer | Luiz Capitulino <lcapitulino@redhat.com> | 2014-09-26 13:14:10 -0400 |
commit | cee2dedb85b97e4976c83bea84064c3921b8b7ac (patch) | |
tree | 4c98449fe16c7d477ae2d43ba8ec85018e0c0597 /savevm.c | |
parent | 1f9296b51a26650916a2c4191268bb64057bdc5f (diff) | |
download | qemu-cee2dedb85b97e4976c83bea84064c3921b8b7ac.zip qemu-cee2dedb85b97e4976c83bea84064c3921b8b7ac.tar.gz qemu-cee2dedb85b97e4976c83bea84064c3921b8b7ac.tar.bz2 |
qapi: add visit_start_union and visit_end_union
In some cases an input visitor might bail out on filling out a
struct for various reasons, such as missing fields when running
in strict mode. In the case of a QAPI Union type, this may lead
to cases where the .kind field which encodes the union type
is uninitialized. Subsequently, other visitors, such as the
dealloc visitor, may use this .kind value as if it were
initialized, leading to assumptions about the union type which
in this case may lead to segfaults. For example, freeing an
integer value.
However, we can generally rely on the fact that the always-present
.data void * field that we generate for these union types will
always be NULL in cases where .kind is uninitialized (at least,
there shouldn't be a reason where we'd do this purposefully).
So pass this information on to Visitor implementation via these
optional start_union/end_union interfaces so this information
can be used to guard against the situation above. We will make
use of this information in a subsequent patch for the dealloc
visitor.
Cc: qemu-stable@nongnu.org
Reported-by: Fam Zheng <famz@redhat.com>
Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Diffstat (limited to 'savevm.c')
0 files changed, 0 insertions, 0 deletions