DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Power, Ciara" <ciara.power@intel.com>
To: "Bronowski, PiotrX" <piotrx.bronowski@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"gakhil@marvell.com" <gakhil@marvell.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Doherty, Declan" <declan.doherty@intel.com>,
	"Bronowski, PiotrX" <piotrx.bronowski@intel.com>,
	 "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v4] crypto/ipsec_mb: fix coverity issue
Date: Thu, 10 Mar 2022 09:17:50 +0000	[thread overview]
Message-ID: <MN2PR11MB3821A6A2F311873D5A9FD9B1E60B9@MN2PR11MB3821.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220309180200.1864114-1-piotrx.bronowski@intel.com>

>-----Original Message-----
>From: Piotr Bronowski <piotrx.bronowski@intel.com>
>Sent: Wednesday 9 March 2022 18:02
>To: dev@dpdk.org
>Cc: Zhang, Roy Fan <roy.fan.zhang@intel.com>; thomas@monjalon.net;
>gakhil@marvell.com; Yigit, Ferruh <ferruh.yigit@intel.com>; Doherty, Declan
><declan.doherty@intel.com>; Bronowski, PiotrX
><piotrx.bronowski@intel.com>; stable@dpdk.org
>Subject: [PATCH v4] crypto/ipsec_mb: fix coverity issue
>
>This patch removes coverity defect CID 375828:
>Untrusted value as argument (TAINTED_SCALAR)
>
>Coverity issue: CID 375828
>
>Fixes: ceb863938708 ("crypto/aesni_gcm: support all truncated digest sizes")
>
>Signed-off-by: Piotr Bronowski <piotrx.bronowski@intel.com>
>
>Cc: stable@dpdk.org
>
>---
>v4: commit message corrected
>---
> drivers/crypto/ipsec_mb/pmd_aesni_gcm.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
<snip>

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

  reply	other threads:[~2022-03-10  9:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 12:48 [PATCH] crypto/ipsec_mb: fix usage of untrusted value Piotr Bronowski
2022-03-07 15:32 ` [PATCH v2] " Piotr Bronowski
2022-03-07 16:26   ` Zhang, Roy Fan
2022-03-09 13:19     ` Ji, Kai
2022-03-09 14:34     ` Zhang, Roy Fan
2022-03-09 14:40       ` Power, Ciara
2022-03-09 15:08   ` [PATCH v3] crypto/ipsec_mb: fix coverity issue Piotr Bronowski
2022-03-09 18:02     ` [PATCH v4] " Piotr Bronowski
2022-03-10  9:17       ` Power, Ciara [this message]
2022-03-14 10:32         ` Thomas Monjalon

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=MN2PR11MB3821A6A2F311873D5A9FD9B1E60B9@MN2PR11MB3821.namprd11.prod.outlook.com \
    --to=ciara.power@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gakhil@marvell.com \
    --cc=piotrx.bronowski@intel.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).