mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Robin van der Gracht <robin@protonic.nl>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] lib: parameter: Free previous string value in param_string_set
Date: Thu, 16 Jun 2022 15:50:30 +0200	[thread overview]
Message-ID: <20220616135030.GX1615@pengutronix.de> (raw)
In-Reply-To: <20220616125040.212193-1-robin@protonic.nl>

On Thu, Jun 16, 2022 at 02:50:40PM +0200, Robin van der Gracht wrote:
> When the parameter has no set function the previous (saved_value) is not
> freed up on completion.
> 
> Signed-off-by: Robin van der Gracht <robin@protonic.nl>
> ---
>  lib/parameter.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/lib/parameter.c b/lib/parameter.c
> index adc3c7cdea..fe7e7b1ba4 100644
> --- a/lib/parameter.c
> +++ b/lib/parameter.c
> @@ -262,8 +262,10 @@ static int param_string_set(struct device_d *dev, struct param_d *p, const char
>  	value_new = strim(value_new);
>  	*ps->value = value_new;
>  
> -	if (!ps->set)
> +	if (!ps->set) {
> +		free(value_save);
>  		return 0;
> +	}

Fixing this bug reveals another one. We do a:

	value_new = xstrdup(val);
	value_new = strim(value_new);

When 'val' has whitespaces at the beginning we no longer free the
pointer originally returned from xstrdup, but the pointer with
whitespaces stripped. I'll queue a fix for this before this patch.

Sascha

-- 
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-06-16 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 12:50 Robin van der Gracht
2022-06-16 13:50 ` Sascha Hauer [this message]
2022-06-16 15:02   ` Robin van der Gracht

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=20220616135030.GX1615@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=robin@protonic.nl \
    /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