From: "Ji, Kai" <kai.ji@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
"pallard, didier" <didier.pallard@6wind.com>
Cc: dpdk stable <stable@dpdk.org>, Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>,
"asekhar@marvell.com" <asekhar@marvell.com>
Subject: Re: [PATCH] crypto/openssl: fix memory leak in auth processing function
Date: Tue, 20 Jun 2023 10:01:51 +0000 [thread overview]
Message-ID: <SN6PR11MB34086C12F50B0ED92AB90687815CA@SN6PR11MB3408.namprd11.prod.outlook.com> (raw)
In-Reply-To: <SN7PR11MB763991660B6600688B66C5E3E65CA@SN7PR11MB7639.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
Acked-by: Kai Ji <kai.ji@intel.com<mailto:kai.ji@intel.com>>
> -----Original Message-----
> From: Didier Pallard <didier.pallard@6wind.com>
> Sent: Tuesday 18 April 2023 15:26
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Ji, Kai <kai.ji@intel.com>; Akhil Goyal
> <gakhil@marvell.com>; Fan Zhang <fanzhang.oss@gmail.com>; Ashwin
> Sekhar T K <asekhar@marvell.com>
> Subject: [PATCH] crypto/openssl: fix memory leak in auth processing
> function
>
> Contexts allocated with EVP_MAC_CTX_new calls are leaking, they are
> created then overwritten by the return value of EVP_MAC_CTX_dup call.
>
> Fixes: 75adf1eae44f ("crypto/openssl: update HMAC routine with 3.0 EVP
> API")
> Fixes: 2b9c693f6ef5 ("crypto/openssl: support AES-CMAC operations")
> Signed-off-by: Didier Pallard <didier.pallard@6wind.com>
> Cc: stable@dpdk.org
> ---
> --
> 2.30.2
[-- Attachment #2: Type: text/html, Size: 1672 bytes --]
next prev parent reply other threads:[~2023-06-20 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 14:26 Didier Pallard
[not found] ` <SN7PR11MB763991660B6600688B66C5E3E65CA@SN7PR11MB7639.namprd11.prod.outlook.com>
2023-06-20 10:01 ` Ji, Kai [this message]
2023-06-20 11:00 ` Akhil Goyal
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=SN6PR11MB34086C12F50B0ED92AB90687815CA@SN6PR11MB3408.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=asekhar@marvell.com \
--cc=dev@dpdk.org \
--cc=didier.pallard@6wind.com \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=stable@dpdk.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).