DPDK patches and discussions
 help / color / mirror / Atom feed

From: Olivier Matz <olivier.matz@6wind.com>
To: Mesut Ali Ergin <mesut.a.ergin@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] kvargs: trim spaces at the beginning and end of key and values
Date: Mon, 1 Jul 2019 15:10:54 +0200	[thread overview]
Message-ID: <20190701131054.7b5nmhkusuncxaoc@platinum> (raw)
In-Reply-To: <1557985267-280205-1-git-send-email-mesut.a.ergin@intel.com>

Hi,

On Wed, May 15, 2019 at 10:41:07PM -0700, Mesut Ali Ergin wrote:
> When arguments delimited with RTE_KVARGS_PAIRS_DELIM happen to have
> spaces before and after the delimiter, the rte_kvargs_process() can not
> match them to the intended key. For example, the first argument below
> triggers the support-multi-driver handler as expected, but the second
> one silently fails to do so.
> 
> -w '84:00.0,support-multi-driver=1'
> -w '84:00.0, support-multi-driver=1'
> 
> Signed-off-by: Mesut Ali Ergin <mesut.a.ergin@intel.com>
> ---
>  lib/librte_kvargs/rte_kvargs.c | 32 ++++++++++++++++++++++++++++++--
>  1 file changed, 30 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/librte_kvargs/rte_kvargs.c b/lib/librte_kvargs/rte_kvargs.c
> index f7030c6..1f45bc6 100644
> --- a/lib/librte_kvargs/rte_kvargs.c
> +++ b/lib/librte_kvargs/rte_kvargs.c
> @@ -10,6 +10,32 @@
>  
>  #include "rte_kvargs.h"
>  
> +
> +/* trim leading and trailing spaces */
> +static char *
> +trim_space(char *str)
> +{
> +	char *start, *end;
> +
> +	for (start = str; *start; start++) {
> +		if (!isspace((unsigned char) start[0]))
> +			break;
> +	}
> +
> +	for (end = start + strlen(start); end > start + 1; end--) {
> +		if (!isspace((unsigned char) end[-1]))
> +			break;
> +	}
> +
> +	*end = 0;
> +
> +	/* Shift from "start" to the beginning of the string */
> +	if (start > str)
> +		memmove(str, start, (end - start) + 1);
> +
> +	return str;
> +}
> +
>  /*
>   * Receive a string with a list of arguments following the pattern
>   * key=value,key=value,... and insert them into the list.
> @@ -38,8 +64,10 @@ rte_kvargs_tokenize(struct rte_kvargs *kvlist, const char *params)
>  		if (i >= RTE_KVARGS_MAX)
>  			return -1;
>  
> -		kvlist->pairs[i].key = strtok_r(str, RTE_KVARGS_KV_DELIM, &ctx2);
> -		kvlist->pairs[i].value = strtok_r(NULL, RTE_KVARGS_KV_DELIM, &ctx2);
> +		kvlist->pairs[i].key = trim_space(strtok_r(str,
> +			RTE_KVARGS_KV_DELIM, &ctx2));
> +		kvlist->pairs[i].value = trim_space(strtok_r(NULL,
> +			RTE_KVARGS_KV_DELIM, &ctx2));
>  		if (kvlist->pairs[i].key == NULL ||
>  		    kvlist->pairs[i].value == NULL)
>  			return -1;

Having a space in the kwvargs strings like in your example
(-w '84:00.0, support-multi-driver=1') is wrong. I don't think we should
fix this in kvargs library.

I you feel it is necessary, we could potentially add a comment in the API
description to highlight this.


Thanks,
Olivier

     prev parent reply	other threads:[~2019-07-01 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  5:41 Mesut Ali Ergin
2019-05-16  5:41 ` Mesut Ali Ergin
2019-05-16 16:36 ` Stephen Hemminger
2019-05-16 20:55   ` Ergin, Mesut A
2019-05-16 23:18     ` Stephen Hemminger
2019-07-01 13:10 ` Olivier Matz [this message]

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=20190701131054.7b5nmhkusuncxaoc@platinum \
    --to=olivier.matz@6wind.com \
    --cc=dev@dpdk.org \
    --cc=mesut.a.ergin@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

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).