@@ -138,6 +138,10 @@ void visit_type_%(c_name)s(Visitor *v, %(c_name)s **obj, const char *name, Error
def gen_visit_list(name, element_type):
+ # FIXME: if *obj is NULL on entry, and the first visit_next_list()
+ # assigns to *obj, while a later one fails, we should clean up *obj
+ # rather than leaving it non-NULL. As currently written, the caller must
+ # call qapi_free_FOOList() to avoid a memory leak of the partial FOOList.
return mcgen('''
void visit_type_%(c_name)s(Visitor *v, %(c_name)s **obj, const char *name, Error **errp)
@@ -701,6 +701,7 @@ static void test_visitor_in_errors(TestInputVisitorData *data,
{
TestStruct *p = NULL;
Visitor *v;
+ strList *q = NULL;
v = visitor_input_test_init(data, "{ 'integer': false, 'boolean': 'foo', 'string': -42 }");
@@ -712,6 +713,15 @@ static void test_visitor_in_errors(TestInputVisitorData *data,
g_free(p->string);
g_free(p);
+
+ v = visitor_input_test_init(data, "[ '1', '2', false, '3' ]");
+ /* FIXME - a failed parse should not leave a partially-allocated
+ * array for us to clean up; this could cause callers to leak
+ * memory. */
+ visit_type_strList(v, &q, NULL, &data->err);
+ assert(q);
+ assert(data->err);
+ qapi_free_strList(q);
}
int main(int argc, char **argv)
Our generated list visitors have the same problem as has been mentioned elsewhere (see commit 2f52e20): they allocate data even on failure. An upcoming patch will correct things to provide saner guarantees, but first we need to expose the behavior in the testsuite to ensure we aren't introducing any memory usage bugs. Signed-off-by: Eric Blake <eblake@redhat.com> --- v9: move earlier in series (was 15/17) v8: no change v7: no change v6: rebase onto earlier gen_err_check() and testsuite improvements --- scripts/qapi-visit.py | 4 ++++ tests/test-qmp-input-visitor.c | 10 ++++++++++ 2 files changed, 14 insertions(+)