From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "olivier.matz@6wind.com" <olivier.matz@6wind.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Glynn, Michael J" <michael.j.glynn@intel.com>,
"Liu, Yu Y" <yu.y.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] lib/librte_cmdline: fix CLI parsing issue
Date: Fri, 28 Apr 2017 08:38:21 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B59DB03@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1493089885-94889-1-git-send-email-wenzhuo.lu@intel.com>
Hi Oilvier,
As we discussed before, I send this patch. Would you like to take a look at it? Better fix it before release 17.05, thanks.
> -----Original Message-----
> From: Lu, Wenzhuo
> Sent: Tuesday, April 25, 2017 11:11 AM
> To: dev@dpdk.org
> Cc: olivier.matz@6wind.com; Lu, Wenzhuo; stable@dpdk.org
> Subject: [PATCH] lib/librte_cmdline: fix CLI parsing issue
>
> When parsing a CLI, all the CLI instances are checked one by one. Even if an
> instance already matches the CLI, the parsing will not stop for ambiguous
> check.
> The problem is that the following check may change the parsing result of the
> previous one even if the following instance doesn't match.
>
> Use a temporary validate for the parsing result when trying to match an
> instance and only store the result when it matches, so the previous result
> has no chance to be changed.
>
> Fixes: af75078fece3 ("first public release")
> CC: stable@dpdk.org
>
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
> ---
> lib/librte_cmdline/cmdline_parse.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/lib/librte_cmdline/cmdline_parse.c
> b/lib/librte_cmdline/cmdline_parse.c
> index 763c286..b814880 100644
> --- a/lib/librte_cmdline/cmdline_parse.c
> +++ b/lib/librte_cmdline/cmdline_parse.c
> @@ -258,7 +258,7 @@
> union {
> char buf[CMDLINE_PARSE_RESULT_BUFSIZE];
> long double align; /* strong alignment constraint for buf */
> - } result;
> + } result, tmp_result;
> cmdline_parse_token_hdr_t
> *dyn_tokens[CMDLINE_PARSE_DYNAMIC_TOKENS];
> void (*f)(void *, struct cmdline *, void *) = NULL;
> void *data = NULL;
> @@ -321,14 +321,16 @@
> debug_printf("INST %d\n", inst_num);
>
> /* fully parsed */
> - tok = match_inst(inst, buf, 0, result.buf, sizeof(result.buf),
> - &dyn_tokens);
> + tok = match_inst(inst, buf, 0, tmp_result.buf,
> + sizeof(tmp_result.buf), &dyn_tokens);
>
> if (tok > 0) /* we matched at least one token */
> err = CMDLINE_PARSE_BAD_ARGS;
>
> else if (!tok) {
> debug_printf("INST fully parsed\n");
> + memcpy(&result, &tmp_result,
> + sizeof(result));
> /* skip spaces */
> while (isblank2(*curbuf)) {
> curbuf++;
> --
> 1.9.3
next prev parent reply other threads:[~2017-04-28 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 3:11 Wenzhuo Lu
2017-04-28 8:38 ` Lu, Wenzhuo [this message]
2017-04-28 9:13 ` Olivier Matz
2017-04-30 22:18 ` Thomas Monjalon
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=6A0DE07E22DDAD4C9103DF62FEBC09093B59DB03@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=dev@dpdk.org \
--cc=michael.j.glynn@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stable@dpdk.org \
--cc=yu.y.liu@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).