public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dfu: avoid memory leak
Date: Fri, 06 May 2016 11:10:18 +0200	[thread overview]
Message-ID: <20160506111018.68b12f17@amdc2363> (raw)
In-Reply-To: <1462242292-1044-1-git-send-email-van.freenix@gmail.com>

Hi Peng,

> When dfu_fill_entity fail, need to free dfu to avoid memory leak.
> 
> Reported by Coverity:
> "
> Resource leak (RESOURCE_LEAK)
> leaked_storage: Variable dfu going out of scope leaks the storage
> it points to.
> "
> 
> Signed-off-by: Peng Fan <van.freenix@gmail.com>
> Cc: "?ukasz Majewski" <l.majewski@samsung.com>
> Cc: Marek Vasut <marex@denx.de>
> ---
>  drivers/dfu/dfu.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/dfu/dfu.c b/drivers/dfu/dfu.c
> index 8f5915e..20dfcbb 100644
> --- a/drivers/dfu/dfu.c
> +++ b/drivers/dfu/dfu.c
> @@ -468,8 +468,10 @@ int dfu_config_entities(char *env, char
> *interface, char *devstr) s = strsep(&env, ";");
>  		ret = dfu_fill_entity(&dfu[i], s, alt_num_cnt,
> interface, devstr);
> -		if (ret)
> +		if (ret) {
> +			free(dfu);
>  			return -1;
> +		}
>  
>  		list_add_tail(&dfu[i].list, &dfu_list);
>  		alt_num_cnt++;

Acked-by: Lukasz Majewski <l.majewski@samsung.com>

Applied to u-boot-dfu tree.

Tested-at: Odroid U3 (Exynos4412)

Thanks for running coverity.



-- 
Best regards,

Lukasz Majewski

Samsung R&D Institute Poland (SRPOL) | Linux Platform Group

      parent reply	other threads:[~2016-05-06  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03  2:24 [U-Boot] [PATCH] dfu: avoid memory leak Peng Fan
2016-05-03 21:29 ` Tom Rini
2016-05-06  9:10 ` Lukasz Majewski [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=20160506111018.68b12f17@amdc2363 \
    --to=l.majewski@samsung.com \
    --cc=u-boot@lists.denx.de \
    /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