From: "Finn, Emma" <emma.finn@intel.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Ji, Kai" <kai.ji@intel.com>
Subject: RE: [EXTERNAL] [PATCH] examples/fips_validation: fix dangling pointer for SHA test
Date: Fri, 29 Aug 2025 10:18:07 +0000 [thread overview]
Message-ID: <CY8PR11MB784530D82EB6D7A7D4EF1F99EA3AA@CY8PR11MB7845.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO1PR18MB471416C114E8D59E97EEBE2FCB3BA@CO1PR18MB4714.namprd18.prod.outlook.com>
> -----Original Message-----
> From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> Sent: Thursday 28 August 2025 10:42
> To: Finn, Emma <emma.finn@intel.com>
> Cc: dev@dpdk.org; Ji, Kai <kai.ji@intel.com>
> Subject: RE: [EXTERNAL] [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;
>
> Same could be the case for fips_mct_shake_test also.
>
Good catch, probably the same could happen with shake.
I currently don’t have a way to test shake but I'm happy to make the change as part of this patch if you can test?
Thanks,
Emma
> Thanks,
> Gowrishankar
> > rte_free(val.val);
> > return 0;
> > }
> > --
> > 2.34.1
next prev parent reply other threads:[~2025-08-29 10:18 UTC|newest]
Thread overview: 7+ 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 [this message]
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
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=CY8PR11MB784530D82EB6D7A7D4EF1F99EA3AA@CY8PR11MB7845.namprd11.prod.outlook.com \
--to=emma.finn@intel.com \
--cc=dev@dpdk.org \
--cc=gmuthukrishn@marvell.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).