From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw120908 [PATCH] examples/ipsec-secgw: set AES-CTR IV length to 16
Date: Wed, 14 Dec 2022 23:17:47 -0500 (EST) [thread overview]
Message-ID: <20221215041747.C4EF710618C@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/120908
_apply patch failure_
Submitter: Tejasree Kondoj <ktejasree@marvell.com>
Date: Thursday, December 15 2022 03:58:05
Applied on: CommitID:c581c49cd3fcaff596fbe566e270b442e6326c79
Apply patch set 120908 failed:
Checking patch examples/ipsec-secgw/sa.c...
error: while searching for:
case RTE_CRYPTO_CIPHER_NULL:
case RTE_CRYPTO_CIPHER_3DES_CBC:
case RTE_CRYPTO_CIPHER_AES_CBC:
case RTE_CRYPTO_CIPHER_AES_CTR:
iv_length = sa->iv_len;
break;
default:
RTE_LOG(ERR, IPSEC_ESP,
"unsupported cipher algorithm %u\n",
error: patch failed: examples/ipsec-secgw/sa.c:1319
Applying patch examples/ipsec-secgw/sa.c with 1 reject...
Rejected hunk #1.
diff a/examples/ipsec-secgw/sa.c b/examples/ipsec-secgw/sa.c (rejected hunks)
@@ -1319,9 +1319,14 @@ sa_add_rules(struct sa_ctx *sa_ctx, const struct ipsec_sa entries[],
case RTE_CRYPTO_CIPHER_NULL:
case RTE_CRYPTO_CIPHER_3DES_CBC:
case RTE_CRYPTO_CIPHER_AES_CBC:
- case RTE_CRYPTO_CIPHER_AES_CTR:
iv_length = sa->iv_len;
break;
+ case RTE_CRYPTO_CIPHER_AES_CTR:
+ /* Length includes 8B per packet IV, 4B nonce and
+ * 4B counter as populated in datapath.
+ */
+ iv_length = 16;
+ break;
default:
RTE_LOG(ERR, IPSEC_ESP,
"unsupported cipher algorithm %u\n",
https://lab.dpdk.org/results/dashboard/patchsets/24740/
UNH-IOL DPDK Community Lab
next reply other threads:[~2022-12-15 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 4:17 dpdklab [this message]
[not found] <20221215035805.1777924-1-ktejasree@marvell.com>
2022-12-15 3:50 ` qemudev
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=20221215041747.C4EF710618C@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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).