From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH v2 7/7] examples/fips_validation: avoid rte_memcpy() bug
Date: Mon, 5 Jan 2026 04:21:38 +0000 [thread overview]
Message-ID: <CO1PR18MB4714A82172593F7EF513DEAFCB86A@CO1PR18MB4714.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20251230185837.301163-8-stephen@networkplumber.org>
Acked-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> Fixes: ae5ae3bf5996 ("examples/fips_validation: encode digest with hash OID")
> Cc: gmuthukrishn@marvell.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> examples/fips_validation/main.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/examples/fips_validation/main.c b/examples/fips_validation/main.c
> index f21826e9d7..daf273bc85 100644
> --- a/examples/fips_validation/main.c
> +++ b/examples/fips_validation/main.c
> @@ -882,8 +882,8 @@ get_hash_oid(enum rte_crypto_auth_algorithm hash,
> uint8_t *buf)
> uint8_t id_sha1[] = {0x30, 0x21, 0x30, 0x09, 0x06, 0x05,
> 0x2b, 0x0e, 0x03, 0x02, 0x1a, 0x05,
> 0x00, 0x04, 0x14};
> - uint8_t *id = NULL;
> - int id_len = 0;
> + const uint8_t *id;
> + size_t id_len;
>
> switch (hash) {
> case RTE_CRYPTO_AUTH_SHA1:
> @@ -907,12 +907,10 @@ get_hash_oid(enum rte_crypto_auth_algorithm hash,
> uint8_t *buf)
> id_len = sizeof(id_sha512);
> break;
> default:
> - id_len = -1;
> - break;
> + return -1;
> }
>
> - if (id != NULL)
> - rte_memcpy(buf, id, id_len);
> + memcpy(buf, id, id_len);
>
> return id_len;
> }
> @@ -1614,8 +1612,8 @@ prepare_rsa_xform(struct rte_crypto_asym_xform
> *xform)
> if (b_len) {
> msg.len = env.digest_len + b_len;
> msg.val = rte_zmalloc(NULL, msg.len, 0);
> - rte_memcpy(msg.val, b, b_len);
> - rte_memcpy(msg.val + b_len, env.digest,
> env.digest_len);
> + memcpy(msg.val, b, b_len);
> + memcpy(msg.val + b_len, env.digest,
> env.digest_len);
> rte_free(env.digest);
> env.digest = msg.val;
> env.digest_len = msg.len;
> --
> 2.51.0
prev parent reply other threads:[~2026-01-05 4:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-28 18:40 [PATCH 0/7] Fix build with gcc-16 Stephen Hemminger
2025-12-28 18:40 ` [PATCH 1/7] pcapng: use alloca instead of fixed buffer Stephen Hemminger
2025-12-28 18:40 ` [PATCH 2/7] pcapng: add additional mbuf if space required on copy Stephen Hemminger
2025-12-28 18:40 ` [PATCH 3/7] test: add more tests for comments in pcapng Stephen Hemminger
2025-12-28 18:40 ` [PATCH 4/7] test: vary size of packets in pcapng test Stephen Hemminger
2025-12-28 18:40 ` [PATCH 5/7] net/bnxt: fix uninitialized warning Stephen Hemminger
2025-12-28 18:40 ` [PATCH 6/7] common/cnxk: fix array out of bounds Stephen Hemminger
2025-12-28 18:40 ` [PATCH 7/7] examples/fips_validation: avoid rte_memcpy alignment restriction Stephen Hemminger
2025-12-30 18:55 ` [PATCH v2 0/7] Fix build with Gcc-16 Stephen Hemminger
2025-12-30 18:55 ` [PATCH v2 1/7] pcapng: use alloca instead of fixed buffer Stephen Hemminger
2025-12-30 18:55 ` [PATCH v2 2/7] pcapng: add additional mbuf if space required on copy Stephen Hemminger
2025-12-30 18:55 ` [PATCH v2 3/7] test: add more tests for comments in pcapng Stephen Hemminger
2025-12-30 18:55 ` [PATCH v2 4/7] test: vary size of packets in pcapng test Stephen Hemminger
2025-12-30 18:55 ` [PATCH v2 5/7] net/bnxt: fix uninitialized warning Stephen Hemminger
2025-12-30 18:55 ` [PATCH v2 6/7] common/cnxk: fix array out of bounds Stephen Hemminger
2025-12-30 18:55 ` [PATCH v2 7/7] examples/fips_validation: avoid rte_memcpy() bug Stephen Hemminger
2026-01-05 4:21 ` Gowrishankar Muthukrishnan [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=CO1PR18MB4714A82172593F7EF513DEAFCB86A@CO1PR18MB4714.namprd18.prod.outlook.com \
--to=gmuthukrishn@marvell.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).