From: Jim Fehlig <jfehlig@suse.com>
To: Joao Martins <joao.m.martins@oracle.com>
Cc: libvir-list@redhat.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v2] libxl: dispose libxl_dominfo after libxl_domain_info()
Date: Thu, 21 Jan 2016 09:58:05 -0700 [thread overview]
Message-ID: <56A10E1D.5010800@suse.com> (raw)
In-Reply-To: <1453371670-3513-1-git-send-email-joao.m.martins@oracle.com>
Joao Martins wrote:
> As suggested in a previous thread [0] this patch adds some missing calls
> to libxl_dominfo_{init,dispose} when doing some of the libxl_domain_info
> operations which would otherwise lead to memory leaks.
>
> [0]
> https://www.redhat.com/archives/libvir-list/2015-September/msg00519.html
>
> Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
> ---
> Changes since v1:
> - Add missing libxl_dominfo_init() on MemoryStats and GetInfo()
> ---
> src/libxl/libxl_driver.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
Thanks, looks good now. ACK and pushed.
Regards,
Jim
prev parent reply other threads:[~2016-01-21 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 10:21 [PATCH v2] libxl: dispose libxl_dominfo after libxl_domain_info() Joao Martins
2016-01-21 16:58 ` Jim Fehlig [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=56A10E1D.5010800@suse.com \
--to=jfehlig@suse.com \
--cc=joao.m.martins@oracle.com \
--cc=libvir-list@redhat.com \
--cc=xen-devel@lists.xen.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).