All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Meng Xu <mengxu@seas.upenn.edu>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-4.7] sched/rt: Fix memory leak in rt_init()
Date: Tue, 10 May 2016 14:57:23 +0100	[thread overview]
Message-ID: <5731E8C3.50503@citrix.com> (raw)
In-Reply-To: <CAENZ-+=YudL-6i+Y-4S0WG=EOrjd1RNnZ3Tzni6vqh0oeG-_YA@mail.gmail.com>

On 10/05/16 14:52, Meng Xu wrote:
> On Tue, May 10, 2016 at 9:38 AM, Andrew Cooper
> <andrew.cooper3@citrix.com> wrote:
>> c/s 2656bc7b0 "xen: adopt .deinit_pdata and improve timer handling"
>> introduced a error path into rt_init() which leaked prv if the
>> allocation of prv->repl_timer failed.
>>
>> Introduce an error cleanup path.
>>
>> Spotted by Coverity.
> I'm curious about this line. Does it mean that this is spotted by the
> coverty code review or by some automatical testing/checking?

XenServer has our Coverity instance hooked up to every build.

Every time I pull a new version of staging, I get a Coverity report as a
delta from the last build.

>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>> ---
> I'm sorry that I should have spot it out when I reviewed the code. :-(

No worries - if this was easy to start with, tools like Coverity
wouldn't exist ;)

>
> Reviewed-by: Meng Xu <mengxu@cis.upenn.edu>

Thanks,

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-05-10 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 13:38 [PATCH for-4.7] sched/rt: Fix memory leak in rt_init() Andrew Cooper
2016-05-10 13:52 ` Meng Xu
2016-05-10 13:57   ` Andrew Cooper [this message]
2016-05-10 14:18 ` Wei Liu
2016-05-10 14:18   ` Andrew Cooper

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=5731E8C3.50503@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=mengxu@seas.upenn.edu \
    --cc=wei.liu2@citrix.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 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.