From: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
To: qemu devel <qemu-devel@nongnu.org>,
Jason Wang <jasowang@redhat.com>, Eric Blake <eblake@redhat.com>
Cc: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
Li Zhijian <lizhijian@cn.fujitsu.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH V4] colo-proxy: fix memory leak
Date: Mon, 17 Oct 2016 17:23:58 +0800 [thread overview]
Message-ID: <1476696239-21655-1-git-send-email-zhangchen.fnst@cn.fujitsu.com> (raw)
Fix memory leak in colo-compare.c and filter-rewriter.c
Report by Coverity and add some comments.
v3:
- rebase this patch for upstream codes
v2:
- use traces instead of fprintf in colo-compare.c
v1:
- initial patch
Zhang Chen (1):
colo-proxy: fix memory leak
net/colo-compare.c | 34 +++++++++++++++-------------------
net/filter-rewriter.c | 17 +++++------------
net/trace-events | 1 +
3 files changed, 21 insertions(+), 31 deletions(-)
--
2.7.4
next reply other threads:[~2016-10-17 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 9:23 Zhang Chen [this message]
2016-10-17 9:23 ` [Qemu-devel] [PATCH V4] colo-proxy: fix memory leak Zhang Chen
2016-10-24 1:58 ` Zhang Chen
2016-10-24 3:08 ` Hailiang Zhang
2016-10-26 1:54 ` Jason Wang
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=1476696239-21655-1-git-send-email-zhangchen.fnst@cn.fujitsu.com \
--to=zhangchen.fnst@cn.fujitsu.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).