From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>,
Harmandeep Kaur <write.harmandeep@gmail.com>
Cc: xen-devel@lists.xenproject.org, dario.faggioli@citrix.com,
ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v3] libxc: fix leak of t_info in xc_tbuf_get_size()
Date: Thu, 18 Feb 2016 11:58:40 +0000 [thread overview]
Message-ID: <1455796720.6225.41.camel@citrix.com> (raw)
In-Reply-To: <20160212123443.GB3036@citrix.com>
On Fri, 2016-02-12 at 12:34 +0000, Wei Liu wrote:
> On Fri, Feb 12, 2016 at 04:38:32PM +0530, Harmandeep Kaur wrote:
> > Avoid leaking the memory mapping of the trace buffer
> >
> > Coverity ID 1351228
> >
> > Signed-off-by: Harmandeep Kaur <write.harmandeep@gmail.com>
> > Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
>
> Acked-by: Wei Liu <wei.liu2@citrix.com>
Applied, thanks.
Ian.
prev parent reply other threads:[~2016-02-18 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 11:08 [PATCH v3] libxc: fix leak of t_info in xc_tbuf_get_size() Harmandeep Kaur
2016-02-12 12:34 ` Wei Liu
2016-02-18 11:58 ` Ian Campbell [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=1455796720.6225.41.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=write.harmandeep@gmail.com \
--cc=xen-devel@lists.xenproject.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).