From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Harmandeep Kaur <write.harmandeep@gmail.com>
Cc: xen-devel@lists.xenproject.org, dario.faggioli@citrix.com,
wei.liu2@citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v2] libxc: fix leak in xc_offline_page error path
Date: Thu, 11 Feb 2016 15:37:23 +0000 [thread overview]
Message-ID: <1455205043.814.67.camel@citrix.com> (raw)
In-Reply-To: <22203.9289.206432.997176@mariner.uk.xensource.com>
On Wed, 2016-02-10 at 11:51 +0000, Ian Jackson wrote:
> Harmandeep Kaur writes ("[PATCH v2] libxc: fix leak in xc_offline_page
> error path"):
> > Avoid leaking the mapping of the m2p in one of the possible failure
> > cases.
> >
> > Coverity CID 1351225
> >
> > Signed-off-by: Harmandeep Kaur <write.harmandeep@gmail.com>
>
> Thanks.
>
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
applied, including...
> Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
>
> You would put that right after the Reviewed-by.
...this.
FTR I was unsure if xc_unmap_domain_meminfo would be safe to call after a
failed xc_map_domain_meminfo (which it should be, but with libxc you never
can tell) and I think it is indeed safe, although the failure paths in
xc_map_domain_meminfo are pretty complicated they do appear to always reset
fields in the struct to the "free" state.
>
>
> However, there is no need to resend your patch for this. It is normal
> for a committer to search the thread for acks to the patch which
> arrive after it was posted, and fold them in.
>
> In this case since the Subject has changed, someone needs to make sure
> that that search turns up the review, but this message of mine will
> serve that purpose.
>
>
> So, having said all that, thanks for your contribution :-).
>
> Regards,
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-02-11 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 11:19 [PATCH v2] libxc: fix leak in xc_offline_page error path Harmandeep Kaur
2016-02-10 11:51 ` Ian Jackson
2016-02-11 15:37 ` 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=1455205043.814.67.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dario.faggioli@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.