From: Aleksey Kuleshov <rndfax@yandex.ru>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH 1/2] hush: do not do anything if string is zero length
Date: Thu, 18 Aug 2016 11:52:00 +0300 [thread overview]
Message-ID: <105091471510320@web2g.yandex.ru> (raw)
In-Reply-To: <20160818063524.GF20657@pengutronix.de>
>> diff --git a/common/hush.c b/common/hush.c
>> index d3f7bf3..d8fd64b 100644
>> --- a/common/hush.c
>> +++ b/common/hush.c
>> @@ -1655,6 +1655,9 @@ char *shell_expand(char *str)
>> o_string o = {};
>> char *res, *parsed;
>>
>> + if (strlen(str) == 0)
>> + return xstrdup("");
>> +
>
> Can you explain why this is necessary? What happens with an empty string
> without this patch?
/*
* shell_expand - Expand shell variables in a string.
* @str: The input string containing shell variables like
* $var or ${var}
* Return: The expanded string. Must be freed with free().
*/
If shell_expand should be called _only_ with string containing _at least one_ $var or ${var} then this patch is wrong.
And since shell_expand is called only from menutree.c then it's menutree.c's responsibility to verify the string.
Otherwise:
If you pass zero length string (i.e. shell_expand("")) you will end up with "Segmentation Fault"
because this line:
parse_string(&o, &ctx, str);
will give you o.data = NULL
and then comes this line:
parsed = xmemdup(o.data, o.length + 1);
PS. And if you will not fill 'title' file for menu with some data you will get "Segmentation Fault".
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-08-18 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 7:58 [PATCH 0/2] rework menu so that it can support multiline titles Aleksey Kuleshov
2016-08-17 7:58 ` [PATCH 1/2] hush: do not do anything if string is zero length Aleksey Kuleshov
2016-08-18 6:35 ` Sascha Hauer
2016-08-18 8:52 ` Aleksey Kuleshov [this message]
2016-08-17 7:58 ` [PATCH 2/2] rework menu so that it can support multiline titles Aleksey Kuleshov
2016-08-18 7:11 ` Sascha Hauer
2016-08-18 9:36 ` Aleksey Kuleshov
2016-08-18 10:26 ` Sascha Hauer
2016-08-18 10:48 ` Aleksey Kuleshov
2016-08-18 11:24 ` Aleksey Kuleshov
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=105091471510320@web2g.yandex.ru \
--to=rndfax@yandex.ru \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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