From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Zhao1, Wei" <wei.zhao1@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 09:44:47 +0100 [thread overview]
Message-ID: <5cf9b3b8-c615-0554-409e-d161b4245cac@intel.com> (raw)
In-Reply-To: <A2573D2ACFCADC41BB3BE09C6DE313CA07EDB16C@PGSMSX103.gar.corp.intel.com>
On 4/9/2019 8:38 AM, Zhao1, Wei wrote:
> 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 ;) )
>>
>> <...>
>
>
>
> I have change code style as your guide as bellow,
> but strtoul() seems do not work, it return c with a none-null every time.
> you can have a try yourself.
Hi Wei,
Yes it return 'c' none-null, which is OK/expected.
According man page:
"
If endptr is not NULL, strtol() stores the address of the first invalid
character in *endptr. If there were no digits at all, strtol() stores the
original value of nptr in *endptr (and returns 0). In particular, if *nptr is
not '\0' but **endptr is '\0' on return, the entire string is valid.
"
First invalid char in below is 'tmp[2]', which is '0', so 'strtol' returns
'&tmp[2]', this is aligned with what described above.
It says, "if *nptr is not '\0' but **endptr is '\0' on return, the entire string
is valid.", beware it says "**endptr is '\0'", so following check should work:
if (*c != 0) {
len--;
dst[len] = 0;
*size = len;
return -1;
}
>
>
> static int
> parse_hex_string(const char *src, uint8_t *dst, uint32_t *size)
> {
> char *c = NULL;
> uint32_t i, len;
> char tmp[3];
>
> /* Check input parameters */
> if ((src == NULL) ||
> (dst == NULL) ||
> (size == NULL) ||
> (*size == 0))
> return -1;
>
> /* Convert chars to bytes */
> for (i = 0, len = 0; i < *size; i += 2) {
> snprintf(tmp, 3, "%s" ,src + i);
> dst[len++] = strtoul(tmp, &c, 16);
> if(c)
> return -1;
> }
> dst[len] = 0;
> *size = len;
>
> return 0;
> }
>
>>
>>> + /* 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"
next prev parent reply other threads:[~2019-04-09 8:44 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 [this message]
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
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=5cf9b3b8-c615-0554-409e-d161b4245cac@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=wei.zhao1@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).