From: Akhil Goyal <gakhil@marvell.com>
To: Emma Finn <emma.finn@intel.com>, Kai Ji <kai.ji@intel.com>,
Fiona Trahe <fiona.trahe@intel.com>,
Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] [v3 1/2] crypto/qat: fix CCM request descriptor hash_state_sz field
Date: Fri, 14 Nov 2025 15:58:55 +0000 [thread overview]
Message-ID: <CO6PR18MB4484F9DF5C9AB5F558037C88D8CAA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20251112101911.2377840-1-emma.finn@intel.com>
> The hash_state_sz field in the QAT request descriptor for AES-CCM
> operations was incorrectly set to the digest length. According to
> the QAT firmware specification, this field should contain the
> length of AAD in quadwords for CCM operations.
>
> Fixes: ab56c4d9ed9a ("crypto/qat: support AES-CCM")
Cc: stable@dpdk.org
>
> Signed-off-by: Emma Finn <emma.finn@intel.com>
This patch is applied to dpdk-next-crypto
For the second patch please update description.
prev parent reply other threads:[~2025-11-14 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 16:23 [PATCH] " Emma Finn
2025-11-07 16:43 ` Emma Finn
2025-11-10 17:01 ` [v2] " Emma Finn
2025-11-11 14:44 ` Ji, Kai
2025-11-12 4:08 ` Akhil Goyal
2025-11-12 10:19 ` [v3 1/2] " Emma Finn
2025-11-12 10:19 ` [v3 2/2] test/crypto: add QAT AES-CCM test case Emma Finn
2025-11-14 15:29 ` [EXTERNAL] " Akhil Goyal
2025-11-14 16:20 ` [v4] test/crypto: add AES-CCM test case with 32-byte AAD Emma Finn
2025-11-17 18:36 ` [EXTERNAL] " Akhil Goyal
2025-11-14 15:58 ` Akhil Goyal [this message]
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=CO6PR18MB4484F9DF5C9AB5F558037C88D8CAA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=emma.finn@intel.com \
--cc=fanzhang.oss@gmail.com \
--cc=fiona.trahe@intel.com \
--cc=kai.ji@intel.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).