From: "Power, Ciara" <ciara.power@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>
Subject: RE: [PATCH] common/qat: fix null dereference in release function
Date: Mon, 11 Mar 2024 14:39:08 +0000 [thread overview]
Message-ID: <SN7PR11MB7639FC01640341C0B4218B8BE6242@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240308094411.5467-1-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Friday, March 8, 2024 9:44 AM
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Power, Ciara <ciara.power@intel.com>; Kusztal,
> ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH] common/qat: fix null dereference in release function
>
> This commit fixes NULL dereference in the release function, and three additional
> coverity issues related to NULL check.
>
> Coverity issue: 415038
> Coverity issue: 415050
> Coverity issue: 415052
> Coverity issue: 415053
> Fixes: 477d7d051211 ("common/qat: decouple drivers from common code")
>
> Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> drivers/common/qat/qat_device.c | 14 +++++++-------
> drivers/compress/qat/qat_comp_pmd.c | 6 ++++--
> drivers/crypto/qat/qat_asym.c | 5 ++---
> drivers/crypto/qat/qat_sym.c | 4 ++--
> 4 files changed, 15 insertions(+), 14 deletions(-)
>
Acked-by: Ciara Power <ciara.power@intel.com>
next prev parent reply other threads:[~2024-03-11 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 9:44 Arkadiusz Kusztal
2024-03-11 14:39 ` Power, Ciara [this message]
2024-03-13 14:51 ` 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=SN7PR11MB7639FC01640341C0B4218B8BE6242@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@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).