[dpdk-dev,1/5] test: after NULL check, don't free the NULL pointer
Commit Message
In the kvargs test cases, we were checking for errors by checking if the
returned pointer value was NULL. In the error handling, we then tried to
free back the NULL pointer, which would cause a crash.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
app/test/test_kvargs.c | 3 ---
1 file changed, 3 deletions(-)
@@ -78,7 +78,6 @@ static int test_valid_kvargs(void)
kvlist = rte_kvargs_parse(args, valid_keys);
if (kvlist == NULL) {
printf("rte_kvargs_parse() error");
- rte_kvargs_free(kvlist);
goto fail;
}
rte_kvargs_free(kvlist);
@@ -89,7 +88,6 @@ static int test_valid_kvargs(void)
kvlist = rte_kvargs_parse(args, valid_keys);
if (kvlist == NULL) {
printf("rte_kvargs_parse() error");
- rte_kvargs_free(kvlist);
goto fail;
}
/* call check_handler() for all entries with key="check" */
@@ -150,7 +148,6 @@ static int test_valid_kvargs(void)
kvlist = rte_kvargs_parse(args, valid_keys);
if (kvlist == NULL) {
printf("rte_kvargs_parse() error");
- rte_kvargs_free(kvlist);
goto fail;
}
/* call check_handler() on all entries with key="check", it