From: Akhil Goyal <gakhil@marvell.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>, Kai Ji <kai.ji@intel.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: RE: [PATCH] crypto/openssl: fix memory leak
Date: Wed, 17 May 2023 16:48:09 +0000 [thread overview]
Message-ID: <CO6PR18MB4484A5B6A2C2633BBCE5610AD87E9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <96b2fd6a6341603426ad79f71c4bcf1342460e71.1684341281.git.gmuthukrishn@marvell.com>
> Subject: [PATCH] crypto/openssl: fix memory leak
>
> Memory allocated through OPENSSL_malloc should be freed only
> through OPENSSL_free.
>
> Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Patch already submitted.
https://patches.dpdk.org/project/dpdk/patch/20230511135944.142416-1-ciara.power@intel.com/
next prev parent reply other threads:[~2023-05-17 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 16:44 Gowrishankar Muthukrishnan
2023-05-17 16:48 ` Akhil Goyal [this message]
2023-05-17 16:49 ` Ji, Kai
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=CO6PR18MB4484A5B6A2C2633BBCE5610AD87E9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.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).