DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ji, Kai" <kai.ji@intel.com>
To: "Power, Ciara" <ciara.power@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"O'Donovan, Saoirse" <saoirse.odonovan@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] crypto/openssl: fix memory free issue
Date: Thu, 11 May 2023 14:26:36 +0000	[thread overview]
Message-ID: <SN6PR11MB340840F29F1048E13A166D7781749@SN6PR11MB3408.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230511135944.142416-1-ciara.power@intel.com>

Acked-by: Kai Ji <kai.ji@intel.com>

> -----Original Message-----
> From: Power, Ciara <ciara.power@intel.com>
> Sent: Thursday, May 11, 2023 3:00 PM
> To: Ji, Kai <kai.ji@intel.com>
> Cc: dev@dpdk.org; O'Donovan, Saoirse <saoirse.odonovan@intel.com>;
> stable@dpdk.org; Power, Ciara <ciara.power@intel.com>
> Subject: [PATCH] crypto/openssl: fix memory free issue
> 
> From: Saoirse O'Donovan <saoirse.odonovan@intel.com>
> 
> Allocated memory was being freed using 'free' when it should have been
> freed using 'OPENSSL_free'. This has now been modified so that the correct
> method is used to free allocated memory.
> 
> Coverity issue: 384415
> Fixes: 4c7ae22f1f83 ("crypto/openssl: update DSA routine with 3.0 EVP API")
> Cc: kai.ji@intel.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Saoirse O'Donovan <saoirse.odonovan@intel.com>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
> ---

  reply	other threads:[~2023-05-11 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 13:59 Ciara Power
2023-05-11 14:26 ` Ji, Kai [this message]
2023-05-24 12:11   ` 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=SN6PR11MB340840F29F1048E13A166D7781749@SN6PR11MB3408.namprd11.prod.outlook.com \
    --to=kai.ji@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=saoirse.odonovan@intel.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).