DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Power, Ciara" <ciara.power@intel.com>
To: "Ji, Kai" <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	Ray Kinsella <mdr@ashroe.eu>
Subject: RE: [dpdk-dev v1] crypto/ipsec_mb: fix of qp NULL check
Date: Wed, 2 Nov 2022 11:04:15 +0000	[thread overview]
Message-ID: <MN2PR11MB38211F8ACE5E1BCBA06D3856E6399@MN2PR11MB3821.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221101140718.15825-1-kai.ji@intel.com>



> -----Original Message-----
> From: Ji, Kai <kai.ji@intel.com>
> Sent: Tuesday 1 November 2022 14:07
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Ji, Kai <kai.ji@intel.com>; roy.fan.zhang@intel.com;
> De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Ray Kinsella
> <mdr@ashroe.eu>; Power, Ciara <ciara.power@intel.com>
> Subject: [dpdk-dev v1] crypto/ipsec_mb: fix of qp NULL check
> 
> This patch fix the NULL pointer check when dereference qp and ring lookup.
> 
> Coverity issue: 381625
> Fixes: c75542ae4200 ("crypto/ipsec_mb: introduce IPsec_mb framework")
> Cc: roy.fan.zhang@intel.com
> 
> Signed-off-by: Kai Ji <kai.ji@intel.com>
> ---
>  drivers/crypto/ipsec_mb/ipsec_mb_ops.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)

Acked-by: Ciara Power <ciara.power@intel.com>

  reply	other threads:[~2022-11-02 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 14:07 Kai Ji
2022-11-02 11:04 ` Power, Ciara [this message]
2022-11-03  8:08   ` 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=MN2PR11MB38211F8ACE5E1BCBA06D3856E6399@MN2PR11MB3821.namprd11.prod.outlook.com \
    --to=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=kai.ji@intel.com \
    --cc=mdr@ashroe.eu \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=roy.fan.zhang@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).