From: Nithinsen Kaithakadan <nkaithakadan@marvell.com>
To: <dev@dpdk.org>, <stable@dpdk.org>
Cc: <adwivedi@marvell.com>, <anoobj@marvell.com>,
<ktejasree@marvell.com>, <gakhil@marvell.com>,
<fanzhang.oss@gmail.com>
Subject: [PATCH 2/3] test/crypto: set iv len to 32B for auth and cipher
Date: Wed, 18 Jun 2025 12:54:08 +0000 [thread overview]
Message-ID: <20250618125410.767919-3-nkaithakadan@marvell.com> (raw)
In-Reply-To: <20250618125410.767919-1-nkaithakadan@marvell.com>
Set maximum IV length to 32 bytes to include both auth IV
and cipher IV.
Fixes: fd01a9be38d5 ("test/crypto: move IV to crypto op private data")
Signed-off-by: Nithinsen Kaithakadan <nkaithakadan@marvell.com>
---
app/test/test_cryptodev.h | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/app/test/test_cryptodev.h b/app/test/test_cryptodev.h
index a80c11baf4..e243cf945a 100644
--- a/app/test/test_cryptodev.h
+++ b/app/test/test_cryptodev.h
@@ -40,7 +40,11 @@
#define TRUNCATED_DIGEST_BYTE_LENGTH_SHA384 (24)
#define TRUNCATED_DIGEST_BYTE_LENGTH_SHA512 (32)
-#define MAXIMUM_IV_LENGTH (16)
+/*
+ * maximum IV length need to include both the
+ * auth IV length (16 bytes) and the cipher IV length (16 bytes)
+ */
+#define MAXIMUM_IV_LENGTH (32)
#define AES_GCM_J0_LENGTH (16)
#define IV_OFFSET (sizeof(struct rte_crypto_op) + \
--
2.48.1
next prev parent reply other threads:[~2025-06-18 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 12:54 [PATCH 0/3] fixes and addition of aes ctr test vectors Nithinsen Kaithakadan
2025-06-18 12:54 ` [PATCH 1/3] test/crypto: add ctr test cases and vectors Nithinsen Kaithakadan
2025-06-18 12:54 ` Nithinsen Kaithakadan [this message]
2025-06-18 12:54 ` [PATCH 3/3] test/crypto: set ptr to null post crypto op free Nithinsen Kaithakadan
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=20250618125410.767919-3-nkaithakadan@marvell.com \
--to=nkaithakadan@marvell.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=ktejasree@marvell.com \
--cc=stable@dpdk.org \
/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).