From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] app/testpmd: fix support of hex string parser for flow API
Date: Tue, 9 Apr 2019 07:42:49 +0000 [thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07EDB197@PGSMSX103.gar.corp.intel.com> (raw)
Message-ID: <20190409074249.v-qMwSvG5MOgPCZxwKbz7PSBlgaeQdDBWIxAMEuX0aM@z> (raw)
In-Reply-To: <dcb1eb47-af78-abcc-32ce-68919eb57740@intel.com>
Hi, Ferruh
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Friday, March 22, 2019 10:56 PM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Cc: stable@dpdk.org; stephen@networkplumber.org; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>
> Subject: Re: [dpdk-stable] [PATCH v3] app/testpmd: fix support of hex string
> parser for flow API
>
> On 3/22/2019 3:15 AM, Wei Zhao wrote:
> > There is need for users to set configuration of HEX number for RSS
> > key. The key byte should be pass down as hex number not as char
> > string. This patch enable cmdline flow parse HEX number, in order to
> > not using string which pass ASIC number.
> >
> > Fixes: f4d623f96119 ("app/testpmd: fix missing RSS fields in flow
> > action")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> > Tested-by: Peng Yuan <yuan.peng@intel.com>
>
> <...>
>
> > @@ -4475,6 +4486,138 @@ parse_string(struct context *ctx, const struct
> token *token,
> > return -1;
> > }
> >
> > +static uint32_t
> > +get_hex_val(char c)
> > +{
> > + switch (c) {
> > + case '0': case '1': case '2': case '3': case '4': case '5':
> > + case '6': case '7': case '8': case '9':
> > + return c - '0';
> > + case 'A': case 'B': case 'C': case 'D': case 'E': case 'F':
> > + return c - 'A' + 10;
> > + case 'a': case 'b': case 'c': case 'd': case 'e': case 'f':
> > + return c - 'a' + 10;
> > + default:
> > + return 0;
> > + }
> > +}
> > +
> > +static int
> > +parse_hex_string(const char *src, uint8_t *dst, uint32_t *size) {
> > + const char *c;
> > + uint32_t i;
> > +
> > + /* Check input parameters */
> > + if ((src == NULL) ||
> > + (dst == NULL) ||
> > + (size == NULL) ||
> > + (*size == 0))
> > + return -1;
> > + if ((*size & 1) != 0)
> > + return -1;
> > +
> > + for (c = src, i = 0; i < *size; c++, i++) {
> > + if (isxdigit(*c))
> > + continue;
> > + else
> > + return -1;
> > + }
> > +
> > + *size = *size / 2;
> > +
> > + /* Convert chars to bytes */
> > + for (i = 0; i < *size; i++)
> > + dst[i] = get_hex_val(src[2 * i]) * 16 +
> > + get_hex_val(src[2 * i + 1]);
> > +
> > + return 0;
> > +}
>
> I can see this has been discussed already but what would you think updating
> the 'parse_hex_string' something like following, it is less code to maintain:
>
> static int
> parse_hex_string(const char *src, uint8_t *dst, uint32_t *size) {
> int len;
> int i
> for (i = 0, len = 0; i < *size; i += 2) {
> char tmp[3];
> snprintf(tmp, 3, src + i);
> dst[len++] = strtoul(tmp, NULL, 16);
> }
> dst[len] = 0;
> *size = len;
> return 0;
> }
>
> (indeed with better error checking on strtoul ;) )
>
> <...>
>
> > + /* Output buffer is not necessarily NUL-terminated. */
> > + memcpy(buf, hex_tmp, hexlen);
> > + memset((uint8_t *)buf + len, 0x00, size - hexlen);
>
> Can't this overflow the 'buf'? since "len = 2 * hexlen"
> I guess intention is "buf + hexlen"
Yes, you are right, update in v4
next prev parent reply other threads:[~2019-04-09 7:42 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 8:43 [dpdk-dev] [PATCH] " Wei Zhao
2019-03-15 8:43 ` Wei Zhao
2019-03-15 9:44 ` Ananyev, Konstantin
2019-03-15 9:44 ` Ananyev, Konstantin
2019-03-18 1:36 ` Zhao1, Wei
2019-03-18 1:36 ` Zhao1, Wei
2019-03-18 8:49 ` Zhao1, Wei
2019-03-18 8:49 ` Zhao1, Wei
2019-03-21 14:03 ` Ananyev, Konstantin
2019-03-21 14:03 ` Ananyev, Konstantin
2019-03-22 1:34 ` Zhao1, Wei
2019-03-22 1:34 ` Zhao1, Wei
2019-03-18 8:16 ` [dpdk-dev] [PATCH v2] " Wei Zhao
2019-03-18 8:16 ` Wei Zhao
2019-03-19 5:23 ` Zhao1, Wei
2019-03-19 5:23 ` Zhao1, Wei
2019-03-22 3:15 ` [dpdk-dev] [PATCH v3] " Wei Zhao
2019-03-22 3:15 ` Wei Zhao
2019-03-22 14:56 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2019-03-22 14:56 ` Ferruh Yigit
2019-03-25 3:39 ` Zhao1, Wei
2019-03-25 3:39 ` Zhao1, Wei
2019-03-25 8:45 ` Ferruh Yigit
2019-03-25 8:45 ` Ferruh Yigit
2019-03-25 9:25 ` Zhao1, Wei
2019-03-25 9:25 ` Zhao1, Wei
2019-03-25 9:35 ` Ferruh Yigit
2019-03-25 9:35 ` Ferruh Yigit
2019-03-25 9:39 ` Zhao1, Wei
2019-03-25 9:39 ` Zhao1, Wei
2019-04-09 7:38 ` Zhao1, Wei
2019-04-09 7:38 ` Zhao1, Wei
2019-04-09 8:44 ` Ferruh Yigit
2019-04-09 8:44 ` Ferruh Yigit
2019-04-09 9:12 ` Zhao1, Wei
2019-04-09 9:12 ` Zhao1, Wei
2019-04-09 7:40 ` Zhao1, Wei
2019-04-09 7:40 ` Zhao1, Wei
2019-04-09 7:42 ` Zhao1, Wei [this message]
2019-04-09 7:42 ` Zhao1, Wei
2019-04-09 8:41 ` [dpdk-dev] [PATCH v4] " Wei Zhao
2019-04-09 8:41 ` Wei Zhao
2019-04-11 18:40 ` Ferruh Yigit
2019-04-11 18:40 ` Ferruh Yigit
2019-03-18 15:27 ` [dpdk-dev] [PATCH] " Stephen Hemminger
2019-03-18 15:27 ` Stephen Hemminger
2019-03-22 1:34 ` Zhao1, Wei
2019-03-22 1:34 ` Zhao1, Wei
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=A2573D2ACFCADC41BB3BE09C6DE313CA07EDB197@PGSMSX103.gar.corp.intel.com \
--to=wei.zhao1@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).