mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] blspec: fix memory leak handling NFS URLs
Date: Tue, 13 Sep 2022 10:16:17 +0200	[thread overview]
Message-ID: <20220913081617.GJ6477@pengutronix.de> (raw)
In-Reply-To: <20220905070247.538308-1-a.fatoum@pengutronix.de>

On Mon, Sep 05, 2022 at 09:02:47AM +0200, Ahmad Fatoum wrote:
> parse_nfs_url() returns either an allocated string on success or an
> error pointer otherwise. blspec_bootentry_provider() will early
> exit if the path couldn't be resolved and thus not free() the string.
> 
> Fix this memory leak. While at it, change parse_nfs_url() to return NULL
> on error. The error code is unused and just returning NULL, simplifies
> the code.
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
>  common/blspec.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)

Applied, thanks

Sascha

> 
> diff --git a/common/blspec.c b/common/blspec.c
> index 9bb25ee72123..d391f690ad0c 100644
> --- a/common/blspec.c
> +++ b/common/blspec.c
> @@ -341,10 +341,10 @@ static char *parse_nfs_url(const char *url)
>  	int ret;
>  
>  	if (!IS_ENABLED(CONFIG_FS_NFS))
> -		return ERR_PTR(-ENOSYS);
> +		return NULL;
>  
>  	if (strncmp(url, "nfs://", 6))
> -		return ERR_PTR(-EINVAL);
> +		return NULL;
>  
>  	url += 6;
>  
> @@ -413,7 +413,7 @@ out:
>  	if (ret)
>  		free(mountpath);
>  
> -	return ret ? ERR_PTR(ret) : mountpath;
> +	return ret ? NULL : mountpath;
>  }
>  
>  /*
> @@ -824,12 +824,12 @@ static int blspec_bootentry_provider(struct bootentries *bootentries,
>  	if (*name == '/' || !strncmp(name, "nfs://", 6)) {
>  		char *nfspath = parse_nfs_url(name);
>  
> -		if (!IS_ERR(nfspath))
> +		if (nfspath)
>  			name = nfspath;
>  
>  		ret = stat(name, &s);
>  		if (ret)
> -			return found;
> +			goto out;
>  
>  		if (S_ISDIR(s.st_mode))
>  			ret = blspec_scan_directory(bootentries, name);
> @@ -838,8 +838,8 @@ static int blspec_bootentry_provider(struct bootentries *bootentries,
>  		if (ret > 0)
>  			found += ret;
>  
> -		if (!IS_ERR(nfspath))
> -			free(nfspath);
> +out:
> +		free(nfspath);
>  	}
>  
>  	return found;
> -- 
> 2.30.2
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2022-09-13  8:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05  7:02 Ahmad Fatoum
2022-09-13  8:16 ` Sascha Hauer [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=20220913081617.GJ6477@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox