All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Alrae <leon.alrae@imgtec.com>
To: <arei.gonglei@huawei.com>, <qemu-devel@nongnu.org>
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH 1/3] target-mips: fix memory leak
Date: Tue, 28 Apr 2015 12:46:31 +0100	[thread overview]
Message-ID: <553F7317.6050607@imgtec.com> (raw)
In-Reply-To: <1430212264-9672-2-git-send-email-arei.gonglei@huawei.com>

On 28/04/2015 10:11, arei.gonglei@huawei.com wrote:
> From: Gonglei <arei.gonglei@huawei.com>
> 
> Coveristy reports that variable prom_buf/params_buf going
> out of scope leaks the storage it points to.
> 
> Cc: Aurelien Jarno <aurelien@aurel32.net>
> Cc: Leon Alrae <leon.alrae@imgtec.com>
> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> ---
>  hw/mips/mips_fulong2e.c | 1 +
>  hw/mips/mips_malta.c    | 1 +
>  hw/mips/mips_r4k.c      | 1 +
>  3 files changed, 3 insertions(+)

Reviewed-by: Leon Alrae <leon.alrae@imgtec.com>

Thanks,
Leon



WARNING: multiple messages have this Message-ID (diff)
From: Leon Alrae <leon.alrae@imgtec.com>
To: arei.gonglei@huawei.com, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 1/3] target-mips: fix memory leak
Date: Tue, 28 Apr 2015 12:46:31 +0100	[thread overview]
Message-ID: <553F7317.6050607@imgtec.com> (raw)
In-Reply-To: <1430212264-9672-2-git-send-email-arei.gonglei@huawei.com>

On 28/04/2015 10:11, arei.gonglei@huawei.com wrote:
> From: Gonglei <arei.gonglei@huawei.com>
> 
> Coveristy reports that variable prom_buf/params_buf going
> out of scope leaks the storage it points to.
> 
> Cc: Aurelien Jarno <aurelien@aurel32.net>
> Cc: Leon Alrae <leon.alrae@imgtec.com>
> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> ---
>  hw/mips/mips_fulong2e.c | 1 +
>  hw/mips/mips_malta.c    | 1 +
>  hw/mips/mips_r4k.c      | 1 +
>  3 files changed, 3 insertions(+)

Reviewed-by: Leon Alrae <leon.alrae@imgtec.com>

Thanks,
Leon

  reply	other threads:[~2015-04-28 13:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28  9:11 [Qemu-trivial] [PATCH 0/3] trivial patches arei.gonglei
2015-04-28  9:11 ` [Qemu-devel] " arei.gonglei
2015-04-28  9:11 ` [Qemu-trivial] [PATCH 1/3] target-mips: fix memory leak arei.gonglei
2015-04-28  9:11   ` [Qemu-devel] " arei.gonglei
2015-04-28 11:46   ` Leon Alrae [this message]
2015-04-28 11:46     ` Leon Alrae
2015-04-28  9:11 ` [Qemu-trivial] [PATCH 2/3] xhci: remove unused code arei.gonglei
2015-04-28  9:11   ` [Qemu-devel] " arei.gonglei
2015-04-29  6:48   ` [Qemu-trivial] " Michael Tokarev
2015-04-29  6:48     ` [Qemu-devel] " Michael Tokarev
2015-04-29  7:22     ` [Qemu-trivial] " Gonglei
2015-04-29  7:22       ` Gonglei
2015-05-05  9:55       ` [Qemu-trivial] " Gerd Hoffmann
2015-05-05  9:55         ` Gerd Hoffmann
2015-05-05 10:18   ` [Qemu-trivial] " Michael Tokarev
2015-05-05 10:18     ` [Qemu-devel] " Michael Tokarev
2015-04-28  9:11 ` [Qemu-trivial] [PATCH 3/3] vhost-user: remove superfluous '\n' around error_report() arei.gonglei
2015-04-28  9:11   ` [Qemu-devel] " arei.gonglei
2015-04-28 12:08   ` [Qemu-trivial] " Andreas Färber
2015-04-28 12:08     ` Andreas Färber

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=553F7317.6050607@imgtec.com \
    --to=leon.alrae@imgtec.com \
    --cc=arei.gonglei@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.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.