From: Max Reitz <mreitz@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] vmdk: fix vmdk_parse_extents() extent_file leaks
Date: Thu, 04 Sep 2014 22:11:29 +0200 [thread overview]
Message-ID: <5408C771.9090705@redhat.com> (raw)
In-Reply-To: <1409861083-9634-2-git-send-email-stefanha@redhat.com>
On 04.09.2014 22:04, Stefan Hajnoczi wrote:
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> block/vmdk.c | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Max Reitz <mreitz@redhat.com>
next prev parent reply other threads:[~2014-09-04 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 20:04 [Qemu-devel] [PATCH 0/2] vmdk: fix leaks in vmdk_parse_extents() Stefan Hajnoczi
2014-09-04 20:04 ` [Qemu-devel] [PATCH 1/2] vmdk: fix vmdk_parse_extents() extent_file leaks Stefan Hajnoczi
2014-09-04 20:11 ` Max Reitz [this message]
2014-09-05 4:52 ` Fam Zheng
2014-09-04 20:04 ` [Qemu-devel] [PATCH 2/2] vmdk: fix buf leak in vmdk_parse_extents() Stefan Hajnoczi
2014-09-04 20:13 ` Max Reitz
2014-09-05 4:52 ` Fam Zheng
2014-09-05 9:44 ` [Qemu-devel] [PATCH 0/2] vmdk: fix leaks " Stefan Hajnoczi
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=5408C771.9090705@redhat.com \
--to=mreitz@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).