app/crypto-perf: fix possible overflow

In the latency test, when number of enqueued operations
is less than the burst size, the timestamp value of the
non-enqueued operations was being stored, even though
those operations were being freed.

This could cause an array overflow, since it could store
more values than the total number of operations.

Fixes: 5d75fb09d3be ("app/crypto-perf: fix invalid latency for QAT")
Cc: stable@dpdk.org
Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>

diff --git a/app/test-crypto-perf/cperf_test_latency.c b/app/test-crypto-perf/cperf_test_latency.c
index 3275b4b640c09ccf1cfe3b5be87a8dcc08eef290..e61ac97282d76a81d1387a4c0ec87f8e294c6f75 100644 (file)
--- a/app/test-crypto-perf/cperf_test_latency.c
+++ b/app/test-crypto-perf/cperf_test_latency.c
@@ -396,7 +396,7 @@ cperf_latency_test_runner(void *arg)
                        for (i = ops_enqd; i < burst_size; i++)
                                rte_crypto_op_free(ops[i]);
 
-                       for (i = 0; i < burst_size; i++) {
+                       for (i = 0; i < ops_enqd; i++) {
                                ctx->res[tsc_idx].tsc_start = tsc_start;
                                ops[i]->opaque_data = (void *)&ctx->res[tsc_idx];
                                tsc_idx++;