From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 85A0346BAE for ; Fri, 18 Jul 2025 21:33:46 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 80ED840E44; Fri, 18 Jul 2025 21:33:46 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id DAC1840611 for ; Fri, 18 Jul 2025 21:33:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1752867224; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=W4m12XDUiMY29cj6/aXj0f8KarCPKq2OtQPE2jIqqFE=; b=TuEVygwDK6CvqDl2qq0GAqMFrjNJntD5OdKu+3QPT8nbBDES9gp+5yzOEKllJ9EOWdNW/A Sd5OQM8qkqgSvAFaSraq8TuBW7dl5scVEF1vGN9AxI24GutJTsyXNWP+Nt8QEvoOnmw7Hi PlIKJxLuu+elpDZZ/GjXqfUi5QKrMpw= Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-354-HXgU9LI5PfOovwE1-jrnKQ-1; Fri, 18 Jul 2025 15:33:41 -0400 X-MC-Unique: HXgU9LI5PfOovwE1-jrnKQ-1 X-Mimecast-MFC-AGG-ID: HXgU9LI5PfOovwE1-jrnKQ_1752867220 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id E778119560B5; Fri, 18 Jul 2025 19:33:39 +0000 (UTC) Received: from rh.redhat.com (unknown [10.44.32.40]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 89BAF180045B; Fri, 18 Jul 2025 19:33:38 +0000 (UTC) From: Kevin Traynor To: Shani Peretz Cc: dpdk stable Subject: patch 'app/crypto-perf: fix AAD offset alignment' has been queued to stable release 24.11.3 Date: Fri, 18 Jul 2025 20:29:15 +0100 Message-ID: <20250718193247.1008129-21-ktraynor@redhat.com> In-Reply-To: <20250718193247.1008129-1-ktraynor@redhat.com> References: <20250718193247.1008129-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: Pch6zRVU89154mhh29PFVPh5z6GE01cUhLq5WCzILug_1752867220 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit content-type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Hi, FYI, your patch has been queued to stable release 24.11.3 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 07/23/25. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/kevintraynor/dpdk-stable This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable/commit/0077cade0785e557af763911e0c87e8f239f3f92 Thanks. Kevin --- >From 0077cade0785e557af763911e0c87e8f239f3f92 Mon Sep 17 00:00:00 2001 From: Shani Peretz Date: Tue, 11 Mar 2025 11:01:21 +0200 Subject: [PATCH] app/crypto-perf: fix AAD offset alignment [ upstream commit 7c52aea4e68e0cacc7e41ff08fcddbd513ad7e0a ] AAD offset in AES-GCM crypto test was calculated by adding 16-byte alignment after the IV, which is only needed in AES-CCM. The patch correct the AAD offset calculation in AES-GCM algorithm tests. Fixes: 0b242422d385 ("app/crypto-perf: set AAD after the crypto operation") Signed-off-by: Shani Peretz --- app/test-crypto-perf/cperf_ops.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/app/test-crypto-perf/cperf_ops.c b/app/test-crypto-perf/cperf_ops.c index 6d5f510220..f9be51e17f 100644 --- a/app/test-crypto-perf/cperf_ops.c +++ b/app/test-crypto-perf/cperf_ops.c @@ -689,5 +689,7 @@ cperf_set_ops_aead(struct rte_crypto_op **ops, /* AAD is placed after the IV */ uint16_t aad_offset = iv_offset + - RTE_ALIGN_CEIL(test_vector->aead_iv.length, 16); + ((options->aead_algo == RTE_CRYPTO_AEAD_AES_CCM) ? + RTE_ALIGN_CEIL(test_vector->aead_iv.length, 16) : + test_vector->aead_iv.length); for (i = 0; i < nb_ops; i++) { -- 2.50.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-07-18 20:29:11.815465182 +0100 +++ 0021-app-crypto-perf-fix-AAD-offset-alignment.patch 2025-07-18 20:29:10.825021385 +0100 @@ -1 +1 @@ -From 7c52aea4e68e0cacc7e41ff08fcddbd513ad7e0a Mon Sep 17 00:00:00 2001 +From 0077cade0785e557af763911e0c87e8f239f3f92 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 7c52aea4e68e0cacc7e41ff08fcddbd513ad7e0a ] + @@ -12 +13,0 @@ -Cc: stable@dpdk.org @@ -20 +21 @@ -index 37d06f1dea..47965bbc32 100644 +index 6d5f510220..f9be51e17f 100644 @@ -23 +24 @@ -@@ -723,5 +723,7 @@ cperf_set_ops_aead(struct rte_crypto_op **ops, +@@ -689,5 +689,7 @@ cperf_set_ops_aead(struct rte_crypto_op **ops,