From: Stefan Hajnoczi <stefanha@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: vyasevic@redhat.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] virtio-net: fix the memory leak in rxfilter_notify()
Date: Tue, 19 Nov 2013 09:46:56 +0100 [thread overview]
Message-ID: <20131119084656.GA27265@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1384788737-6233-1-git-send-email-akong@redhat.com>
On Mon, Nov 18, 2013 at 11:32:17PM +0800, Amos Kong wrote:
> object_get_canonical_path() returns a gchar*, it should be freeed by the
> caller.
>
> Signed-off-by: Amos Kong <akong@redhat.com>
> ---
> v2: put gchar *path inside rxfilter_notify_enabled block
> ---
> hw/net/virtio-net.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Thanks, applied to my net tree:
https://github.com/stefanha/qemu/commits/net
Stefan
prev parent reply other threads:[~2013-11-19 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 15:32 [Qemu-devel] [PATCH v2] virtio-net: fix the memory leak in rxfilter_notify() Amos Kong
2013-11-18 15:44 ` Michael S. Tsirkin
2013-11-18 15:51 ` Vlad Yasevich
2013-11-18 15:59 ` Andreas Färber
2013-11-19 8:46 ` Stefan Hajnoczi [this message]
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=20131119084656.GA27265@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=akong@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vyasevic@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).