From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] pan/ltp-pan.c: Add file parsing protection
Date: Fri, 15 Nov 2019 11:03:21 +0100 [thread overview]
Message-ID: <20191115100321.GB18488@rei.lan> (raw)
In-Reply-To: <20191115052906.2643-1-dylan@andestech.com>
Hi!
> A segmentation fault occurs given the wrong format in test cases file.
> for example:
> name command line
> ----- -----------------
> dio10 diotest4 -b 65536 (O)
> dio10 (X)
> dio10 diotest4 -b 65536 (X)
> This patch adds protection and print warning when the command part
> of the tests is empty or multiple whitespaces.
And the expected action here is that we return empty collection when the
file is wrongly formatted and ltp-pan aborts, right?
You should probably write something along these lines here as well.
> Signed-off-by: Dylan Chung <dylan@andestech.com>
> ---
> pan/ltp-pan.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/pan/ltp-pan.c b/pan/ltp-pan.c
> index 8ac484ec6..470bcbfc5 100644
> --- a/pan/ltp-pan.c
> +++ b/pan/ltp-pan.c
> @@ -1200,6 +1200,14 @@ static struct collection *get_collection(char *file, int optind, int argc,
> n->pcnt_f[1] = 's';
> }
> n->name = strdup(strsep(&a, " \t"));
> + while (a != NULL && isspace(*a))
> + a++;
> + if (a == NULL || strlen(a) == 0) {
^
Maybe just || a[0] == 0 there is
no point in using strlen for
checking for empty string...
> + fprintf(stderr,
> + "pan(%s): Testcase '%s' requires a command to execute.\n",
> + panname, n->name);
> + return 0;
^
This should be NULL
> + }
> n->cmdline = strdup(a);
> n->next = NULL;
Otherwise it looks good.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2019-11-15 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 5:29 [LTP] [PATCH] pan/ltp-pan.c: Add file parsing protection Dylan Chung
2019-11-15 10:03 ` Cyril Hrubis [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=20191115100321.GB18488@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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