patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Ciara Power <ciara.power@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"john.mcnamara@intel.com" <john.mcnamara@intel.com>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: RE: [EXT] [PATCH] crypto/ipsec_mb: fix qp cleanup unreachable code
Date: Thu, 17 Feb 2022 18:22:07 +0000	[thread overview]
Message-ID: <CO6PR18MB448407DD9D2D2F71CDA1B7BED8369@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220215110758.149380-1-ciara.power@intel.com>

> The qp is never NULL when it reaches the qp_setup_cleanup error handling
> code. This is due to checks earlier in the function that return an error
> if qp is NULL.
> 
> Coverity issue: 375013
> Fixes: 581c39b1cb7d ("crypto/ipsec_mb: fix queue cleanup null pointer
> dereference")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Ciara Power <ciara.power@intel.com>
Applied to dpdk-next-crypto


      reply	other threads:[~2022-02-17 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 11:07 Ciara Power
2022-02-17 18:22 ` Akhil Goyal [this message]

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=CO6PR18MB448407DD9D2D2F71CDA1B7BED8369@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=roy.fan.zhang@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).