Currently, there is no check if an invalid parameter is passed
to the application.
for example:
./dpdk-test-flow-perf -a 01:00.0 -- --invalid
This validate that all strings are part of the known options.
Fixes: 3344cf2e3001 ("app/flow-perf: add flow performance skeleton")
Cc: wis...@nvidia.com
Cc: sta...@dpdk.org
Signed-off-by: Raslan Darawsheh <rasl...@nvidia.com>
---
app/test-flow-perf/main.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/app/test-flow-perf/main.c b/app/test-flow-perf/main.c
index c1477b14a1..7453cf2b78 100644
--- a/app/test-flow-perf/main.c
+++ b/app/test-flow-perf/main.c
@@ -885,6 +885,13 @@ args_parse(int argc, char **argv)
break;
}
}
+
+ if (opt_idx != argc) {
+ usage(argv[0]);
+ rte_exit(EXIT_FAILURE,
+ "Incorrect command line %s\n", argv[opt_idx]);
+ }
+
if (rules_count % rules_batch != 0) {
rte_exit(EXIT_FAILURE,
"rules_count %% rules_batch should be 0\n");
--
2.25.1
