From: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] Fix hush to give the correct return code for a simple command
Date: Sun, 25 May 2014 10:08:38 +0200 [thread overview]
Message-ID: <5381A506.7070608@herbrechtsmeier.net> (raw)
In-Reply-To: <1400901095-29391-4-git-send-email-sjg@chromium.org>
Am 24.05.2014 05:11, schrieb Simon Glass:
> When a simple command like 'false' is provided, hush should return the
> result of that command. However, hush only does this if the
> FLAG_EXIT_FROM_LOOP flag is provided. Without this flag, hush will
> happily execute the empty string command immediate after 'false' and
> then return a success code.
>
> This behaviour does not seem very useful, and requiring the flag also
> seems wrong, since it means that hush will execute only the first command
> in a sequence.
>
> Add a check for empty string and fall out of the loop in that case. That
> at least fixes the simple command case. This is a change in behaviour but
> it is unlikely that the old behaviour would be considered correct in any
> case.
>
> Reported-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> common/hush.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/common/hush.c b/common/hush.c
> index 5b43224..7a16795 100644
> --- a/common/hush.c
> +++ b/common/hush.c
> @@ -3218,7 +3218,9 @@ static int parse_stream_outer(struct in_str *inp, int flag)
> free_pipe_list(ctx.list_head,0);
> }
> b_free(&temp);
> - } while (rcode != -1 && !(flag & FLAG_EXIT_FROM_LOOP)); /* loop on syntax errors, return on EOF */
> + /* loop on syntax errors, return on EOF */
> + } while (rcode != -1 && !(flag & FLAG_EXIT_FROM_LOOP) &&
> + (inp->peek != static_peek || b_peek(inp)));
> #ifndef __U_BOOT__
> return 0;
> #else
>
Tested-by: Stefan Herbrechtsmeier<stefan@herbrechtsmeier.net>
next prev parent reply other threads:[~2014-05-25 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 3:11 [U-Boot] [PATCH 0/4] Fix a few problems with the command parsers Simon Glass
2014-05-24 3:11 ` [U-Boot] [PATCH 1/4] Add final result tests for run_command_list() Simon Glass
2014-05-24 3:11 ` [U-Boot] [PATCH 2/4] Fix itest mask overflow Simon Glass
2014-05-24 3:11 ` [U-Boot] [PATCH 3/4] Fix hush to give the correct return code for a simple command Simon Glass
2014-05-25 8:08 ` Stefan Herbrechtsmeier [this message]
2014-05-24 3:11 ` [U-Boot] [PATCH 4/4] Correct return code from builtin_run_command_list() Simon Glass
2014-05-30 18:59 ` [U-Boot] [PATCH 0/4] Fix a few problems with the command parsers Tom Rini
2014-05-30 19:16 ` Simon Glass
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=5381A506.7070608@herbrechtsmeier.net \
--to=stefan@herbrechtsmeier.net \
--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