From: Gagandeep Singh <g.singh@nxp.com>
To: dev@dpdk.org, gakhil@marvell.com
Cc: hemant.agrawal@nxp.com
Subject: [PATCH v3 0/6] DPAA2 SEC related changes
Date: Tue, 6 Oct 2026 17:13:40 +0530 [thread overview]
Message-ID: <20261006114346.1229651-1-g.singh@nxp.com> (raw)
In-Reply-To: <20260930070809.1929564-1-g.singh@nxp.com>
V3-changes:
- updated dpaa3_sec.ini with correct feature name.
V2-changes:
- Support AES-GMAC as AUTH algorithm instead of as AEAD.
This series include bug fixes, enhancement and AES-GMAC support
Gagandeep Singh (6):
crypto/dpaa2_sec: fix buffer overflow in GCM decrypt
crypto/dpaa2_sec: fix FLE pool leak on sec FD build failure
crypto/dpaa2_sec: increase ivsize range for AES-CTR
crypto/dpaa2_sec: add missing ECN capability
crypto/dpaa2_sec: add support for env variables
crypto/dpaa2_sec: support AES-GMAC
doc/guides/cryptodevs/dpaa2_sec.rst | 13 +++-
doc/guides/cryptodevs/features/dpaa2_sec.ini | 1 +
drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 78 ++++++++++++++++++--
drivers/crypto/dpaa2_sec/dpaa2_sec_priv.h | 40 ++++++++--
4 files changed, 120 insertions(+), 12 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2026-10-06 11:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 11:29 [PATCH 0/6] DPAA2 SEC related changes Gagandeep Singh
2026-08-10 11:29 ` [PATCH 1/6] crypto/dpaa2_sec: fix buffer overflow in GCM decrypt Gagandeep Singh
2026-08-10 11:29 ` [PATCH 2/6] crypto/dpaa2_sec: fix FLE pool leak on sec FD build failure Gagandeep Singh
2026-08-10 11:29 ` [PATCH 3/6] crypto/dpaa2_sec: support AES-GMAC Gagandeep Singh
2026-08-10 11:29 ` [PATCH 4/6] crypto/dpaa2_sec: increase ivsize range for AES-CTR Gagandeep Singh
2026-08-10 11:29 ` [PATCH 5/6] crypto/dpaa2_sec: add missing ECN capability Gagandeep Singh
2026-08-10 11:29 ` [PATCH 6/6] crypto/dpaa2_sec: add support for env variables Gagandeep Singh
2026-08-10 15:16 ` Stephen Hemminger
2026-08-11 7:50 ` Gagandeep Singh
2026-09-30 7:08 ` [PATCH v2 0/6] DPAA2 SEC related changes Gagandeep Singh
2026-09-30 7:08 ` [PATCH v2 1/6] crypto/dpaa2_sec: fix buffer overflow in GCM decrypt Gagandeep Singh
2026-09-30 7:08 ` [PATCH v2 2/6] crypto/dpaa2_sec: fix FLE pool leak on sec FD build failure Gagandeep Singh
2026-09-30 7:08 ` [PATCH v2 3/6] crypto/dpaa2_sec: increase ivsize range for AES-CTR Gagandeep Singh
2026-09-30 7:08 ` [PATCH v2 4/6] crypto/dpaa2_sec: add missing ECN capability Gagandeep Singh
2026-09-30 7:08 ` [PATCH v2 5/6] crypto/dpaa2_sec: add support for env variables Gagandeep Singh
2026-10-05 18:37 ` [EXTERNAL] " Akhil Goyal
2026-10-06 4:15 ` Gagandeep Singh
2026-09-30 7:08 ` [PATCH v2 6/6] crypto/dpaa2_sec: support AES-GMAC Gagandeep Singh
2026-10-05 18:14 ` [EXTERNAL] " Akhil Goyal
2026-10-06 11:43 ` Gagandeep Singh [this message]
2026-10-06 11:43 ` [PATCH v3 1/6] crypto/dpaa2_sec: fix buffer overflow in GCM decrypt Gagandeep Singh
2026-10-06 11:43 ` [PATCH v3 2/6] crypto/dpaa2_sec: fix FLE pool leak on sec FD build failure Gagandeep Singh
2026-10-06 11:43 ` [PATCH v3 3/6] crypto/dpaa2_sec: increase ivsize range for AES-CTR Gagandeep Singh
2026-10-06 11:43 ` [PATCH v3 4/6] crypto/dpaa2_sec: add missing ECN capability Gagandeep Singh
2026-10-06 11:43 ` [PATCH v3 5/6] crypto/dpaa2_sec: add support for env variables Gagandeep Singh
2026-10-06 11:43 ` [PATCH v3 6/6] crypto/dpaa2_sec: support AES-GMAC Gagandeep Singh
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=20261006114346.1229651-1-g.singh@nxp.com \
--to=g.singh@nxp.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.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