DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Ankur Dwivedi <adwivedi@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "anoobj@marvell.com" <anoobj@marvell.com>,
	"ktejasree@marvell.com" <ktejasree@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/octeontx2: fix null pointer dereferences
Date: Tue, 2 Feb 2021 19:17:14 +0000	[thread overview]
Message-ID: <VI1PR04MB316877769A7167B3D6B806F5E6B59@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20210128051653.20503-1-adwivedi@marvell.com>

> Coverity reports that pointers ip and ip6 may be dereferenced
> with null value. This patch fixes this.
> 
> Coverity issue: 365549
> Coverity issue: 365551
> 
> Fixes: 8f685ec2d545 ("crypto/octeontx2: support AES-CBC SHA1-HMAC")
> 
> Signed-off-by: Ankur Dwivedi <adwivedi@marvell.com>
> ---
> v2:
> * Fixed wrong fixes reference in commit message.
Applied to dpdk-next-crypto

Thanks.


      reply	other threads:[~2021-02-02 19:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 13:35 [dpdk-dev] [PATCH] " Ankur Dwivedi
2021-01-28  5:16 ` [dpdk-dev] [PATCH v2] " Ankur Dwivedi
2021-02-02 19:17   ` 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=VI1PR04MB316877769A7167B3D6B806F5E6B59@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=adwivedi@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ktejasree@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).