From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, armbru@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] Fix leak in handling of integer lists as strings
Date: Mon, 16 May 2016 22:08:55 -0600 [thread overview]
Message-ID: <1463458137-19109-1-git-send-email-eblake@redhat.com> (raw)
The qapi string-input and string-output visitors can leak memory
when used on integer lists that were set up such that the range
list needed to merge adjacent/overlapping ranges; detected by
valgrind on test-string-{input,output}-visitor.
It doesn't hurt that the overall series removes more code than it adds.
Eric Blake (2):
qapi: Simplify use of range.h
qapi: Fix memleak in string visitors on int lists
include/qemu/range.h | 107 +++++++++++++++++--------------------------
qapi/string-input-visitor.c | 17 ++-----
qapi/string-output-visitor.c | 4 +-
3 files changed, 48 insertions(+), 80 deletions(-)
--
2.5.5
next reply other threads:[~2016-05-17 4:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 4:08 Eric Blake [this message]
2016-05-17 4:08 ` [Qemu-devel] [PATCH 1/2] qapi: Simplify use of range.h Eric Blake
2016-05-31 11:45 ` Markus Armbruster
2016-05-17 4:08 ` [Qemu-devel] [PATCH 2/2] qapi: Fix memleak in string visitors on int lists Eric Blake
2016-06-01 6:09 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1463458137-19109-1-git-send-email-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).