From: Anoob Joseph <anoobj@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>,
Ciara Power <ciara.power@intel.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
Jerin Jacob <jerinj@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>, <dev@dpdk.org>
Subject: [PATCH v2] test/crypto: free memory in error and skip paths
Date: Wed, 17 May 2023 16:25:29 +0530 [thread overview]
Message-ID: <20230517105529.405-1-anoobj@marvell.com> (raw)
In-Reply-To: <20230512140946.195-1-anoobj@marvell.com>
In multi session tests, multiple sessions get created. So the handling
in ut_teardown won't guard against any memory that is not freed by the
test case. Test case should free sessions as well as local memory that
was used to save session pointers both in case of unsupported cases as
well as operation failures.
Signed-off-by: Anoob Joseph <anoobj@marvell.com>
---
v2:
* Moved 'ASSERT' to the end to allow cleanup in all cases.
---
app/test/test_cryptodev.c | 59 ++++++++++++++++++++++++++++-----------
1 file changed, 43 insertions(+), 16 deletions(-)
diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
index aaa2ce428d..77187e1fd3 100644
--- a/app/test/test_cryptodev.c
+++ b/app/test/test_cryptodev.c
@@ -12753,8 +12753,8 @@ test_multi_session(void)
struct crypto_testsuite_params *ts_params = &testsuite_params;
struct crypto_unittest_params *ut_params = &unittest_params;
struct rte_cryptodev_info dev_info;
+ int i, nb_sess, ret = TEST_SUCCESS;
void **sessions;
- uint16_t i;
/* Verify the capabilities */
struct rte_cryptodev_sym_capability_idx cap_idx;
@@ -12784,21 +12784,25 @@ test_multi_session(void)
sessions[i] = rte_cryptodev_sym_session_create(
ts_params->valid_devs[0], &ut_params->auth_xform,
ts_params->session_mpool);
- if (sessions[i] == NULL && rte_errno == ENOTSUP)
- return TEST_SKIPPED;
+ if (sessions[i] == NULL && rte_errno == ENOTSUP) {
+ nb_sess = i;
+ ret = TEST_SKIPPED;
+ break;
+ }
TEST_ASSERT_NOT_NULL(sessions[i],
"Session creation failed at session number %u",
i);
+
/* Attempt to send a request on each session */
- TEST_ASSERT_SUCCESS( test_AES_CBC_HMAC_SHA512_decrypt_perform(
+ ret = test_AES_CBC_HMAC_SHA512_decrypt_perform(
sessions[i],
ut_params,
ts_params,
catch_22_quote_2_512_bytes_AES_CBC_ciphertext,
catch_22_quote_2_512_bytes_AES_CBC_HMAC_SHA512_digest,
- aes_cbc_iv),
- "Failed to perform decrypt on request number %u.", i);
+ aes_cbc_iv);
+
/* free crypto operation structure */
rte_crypto_op_free(ut_params->op);
@@ -12817,16 +12821,26 @@ test_multi_session(void)
rte_pktmbuf_free(ut_params->ibuf);
ut_params->ibuf = 0;
}
+
+ if (ret != TEST_SUCCESS) {
+ i++;
+ break;
+ }
}
- for (i = 0; i < MAX_NB_SESSIONS; i++) {
+ nb_sess = i;
+
+ for (i = 0; i < nb_sess; i++) {
rte_cryptodev_sym_session_free(ts_params->valid_devs[0],
sessions[i]);
}
rte_free(sessions);
- return TEST_SUCCESS;
+ if (ret != TEST_SKIPPED)
+ TEST_ASSERT_SUCCESS(ret, "Failed to perform decrypt on request number %u.", i - 1);
+
+ return ret;
}
struct multi_session_params {
@@ -12845,8 +12859,9 @@ test_multi_session_random_usage(void)
{
struct crypto_testsuite_params *ts_params = &testsuite_params;
struct rte_cryptodev_info dev_info;
+ int index = 0, ret = TEST_SUCCESS;
+ uint32_t nb_sess, i, j;
void **sessions;
- uint32_t i, j;
struct multi_session_params ut_paramz[] = {
{
@@ -12905,27 +12920,30 @@ test_multi_session_random_usage(void)
ts_params->valid_devs[0],
&ut_paramz[i].ut_params.auth_xform,
ts_params->session_mpool);
- if (sessions[i] == NULL && rte_errno == ENOTSUP)
- return TEST_SKIPPED;
+ if (sessions[i] == NULL && rte_errno == ENOTSUP) {
+ nb_sess = i;
+ ret = TEST_SKIPPED;
+ goto session_clear;
+ }
TEST_ASSERT_NOT_NULL(sessions[i],
"Session creation failed at session number %u",
i);
}
+ nb_sess = i;
+
srand(time(NULL));
for (i = 0; i < 40000; i++) {
j = rand() % MB_SESSION_NUMBER;
- TEST_ASSERT_SUCCESS(
- test_AES_CBC_HMAC_SHA512_decrypt_perform(
+ ret = test_AES_CBC_HMAC_SHA512_decrypt_perform(
sessions[j],
&ut_paramz[j].ut_params,
ts_params, ut_paramz[j].cipher,
ut_paramz[j].digest,
- ut_paramz[j].iv),
- "Failed to perform decrypt on request number %u.", i);
+ ut_paramz[j].iv);
rte_crypto_op_free(ut_paramz[j].ut_params.op);
@@ -12945,15 +12963,24 @@ test_multi_session_random_usage(void)
rte_pktmbuf_free(ut_paramz[j].ut_params.ibuf);
ut_paramz[j].ut_params.ibuf = 0;
}
+
+ if (ret != TEST_SKIPPED) {
+ index = i;
+ break;
+ }
}
- for (i = 0; i < MB_SESSION_NUMBER; i++) {
+session_clear:
+ for (i = 0; i < nb_sess; i++) {
rte_cryptodev_sym_session_free(ts_params->valid_devs[0],
sessions[i]);
}
rte_free(sessions);
+ if (ret != TEST_SKIPPED)
+ TEST_ASSERT_SUCCESS(ret, "Failed to perform decrypt on request number %u.", index);
+
return TEST_SUCCESS;
}
--
2.25.1
next prev parent reply other threads:[~2023-05-17 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 14:09 [PATCH 1/2] " Anoob Joseph
2023-05-12 14:09 ` [PATCH 2/2] test/crypto: handle return code Anoob Joseph
2023-05-16 10:12 ` Akhil Goyal
2023-05-16 10:45 ` Power, Ciara
2023-05-16 10:53 ` Anoob Joseph
2023-05-16 10:06 ` [PATCH 1/2] test/crypto: free memory in error and skip paths Akhil Goyal
2023-05-17 10:55 ` Anoob Joseph [this message]
2023-05-17 15:44 ` [PATCH v2] " Power, Ciara
2023-05-24 12:41 ` Akhil Goyal
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=20230517105529.405-1-anoobj@marvell.com \
--to=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=ktejasree@marvell.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
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;
as well as URLs for NNTP newsgroup(s).