From: "Ji, Kai" <kai.ji@intel.com>
To: "Finn, Emma" <emma.finn@intel.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] examples/fips_validation: fix dangling pointer for SHA test
Date: Thu, 27 Nov 2025 16:51:41 +0000 [thread overview]
Message-ID: <DS0PR11MB7458615495E52E6745A0DEDA81DFA@DS0PR11MB7458.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250828092822.2791101-1-emma.finn@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
Acked-by: Kai Ji <kai.ji@intel.com>
________________________________
From: Finn, Emma <emma.finn@intel.com>
Sent: 28 August 2025 10:28
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Cc: dev@dpdk.org <dev@dpdk.org>; Ji, Kai <kai.ji@intel.com>; Finn, Emma <emma.finn@intel.com>
Subject: [PATCH] examples/fips_validation: fix dangling pointer for SHA test
Set vector pointer to NULL after free to avoid calling rte_free()
on the same pointer twice in some cases.
Signed-off-by: Emma Finn <emma.finn@intel.com>
---
examples/fips_validation/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/examples/fips_validation/main.c b/examples/fips_validation/main.c
index f21826e9d7..60ee9f8dd4 100644
--- a/examples/fips_validation/main.c
+++ b/examples/fips_validation/main.c
@@ -2612,7 +2612,7 @@ fips_mct_sha_test(void)
rte_free(md[i].val);
rte_free(vec.pt.val);
-
+ vec.pt.val = NULL;
rte_free(val.val);
return 0;
}
--
2.34.1
[-- Attachment #2: Type: text/html, Size: 2277 bytes --]
prev parent reply other threads:[~2025-11-27 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 9:28 Emma Finn
2025-08-28 9:42 ` [EXTERNAL] " Gowrishankar Muthukrishnan
2025-08-29 10:18 ` Finn, Emma
2025-08-29 10:23 ` Gowrishankar Muthukrishnan
2025-08-29 10:40 ` Finn, Emma
2025-08-29 12:16 ` Gowrishankar Muthukrishnan
2025-08-29 13:14 ` Finn, Emma
2025-10-15 15:53 ` Ji, Kai
2025-10-22 5:22 ` Gowrishankar Muthukrishnan
2025-11-27 16:51 ` Ji, Kai [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=DS0PR11MB7458615495E52E6745A0DEDA81DFA@DS0PR11MB7458.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=dev@dpdk.org \
--cc=emma.finn@intel.com \
--cc=gmuthukrishn@marvell.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).