From: Ian Campbell <ian.campbell@citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>,
Harmandeep Kaur <write.harmandeep@gmail.com>,
xen-devel@lists.xenproject.org
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com,
stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] libxc: Fix CID 1351225 resource leak
Date: Wed, 10 Feb 2016 09:48:54 +0000 [thread overview]
Message-ID: <1455097734.19857.128.camel@citrix.com> (raw)
In-Reply-To: <1455096485.3148.168.camel@citrix.com>
On Wed, 2016-02-10 at 10:28 +0100, Dario Faggioli wrote:
> Hi Harmandeep,
>
> Thanks for this patch.
>
> On Wed, 2016-02-10 at 14:37 +0530, Harmandeep Kaur wrote:
> >
> In general, I think it would be best if the subject is a bit more
> "explicative", and if you add a few words of changelog, here, above the
> S-o-b.
>
> In this case, this could be something like this.
>
> Subject: "libxc: fix leak in xc_offline_page error path"
>
> Changelog: "
> 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>
> >
> That being said, this case is very simple, so I'll leave it to the
> tools maintainers to tell whether they want something like what I
> described above in place or not.
I was going to comment the same, so yes please. The subject and commit
message should describe the actual change and the CID should simply be
referenced as Dario has in his example.
>
> The code looks ok to me, so, with or without the subject/changelog
> improvements:
>
> Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
>
> Regards,
> Dario
next prev parent reply other threads:[~2016-02-10 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 9:07 [PATCH] libxc: Fix CID 1351225 resource leak Harmandeep Kaur
2016-02-10 9:28 ` Dario Faggioli
2016-02-10 9:48 ` Ian Campbell [this message]
2016-02-10 11:16 ` Ian Jackson
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=1455097734.19857.128.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 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.