From: Thomas Monjalon <thomas@monjalon.net>
To: "Bronowski, PiotrX" <piotrx.bronowski@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
stable@dpdk.org, "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Power, Ciara" <ciara.power@intel.com>
Subject: Re: [PATCH v4] crypto/ipsec_mb: fix coverity issue
Date: Mon, 14 Mar 2022 11:32:38 +0100 [thread overview]
Message-ID: <44522398.fMDQidcC6G@thomas> (raw)
In-Reply-To: <MN2PR11MB3821A6A2F311873D5A9FD9B1E60B9@MN2PR11MB3821.namprd11.prod.outlook.com>
> >This patch removes coverity defect CID 375828:
> >Untrusted value as argument (TAINTED_SCALAR)
It lacks an explanation of the cause.
> >Coverity issue: CID 375828
You should not write CID above.
> >
> >Fixes: ceb863938708 ("crypto/aesni_gcm: support all truncated digest sizes")
> >
> >Signed-off-by: Piotr Bronowski <piotrx.bronowski@intel.com>
> >
> >Cc: stable@dpdk.org
This Cc should be just below the "Fixes".
> Acked-by: Ciara Power <ciara.power@intel.com>
Fixed formatting, writing a better title, and applied.
prev parent reply other threads:[~2022-03-14 10:32 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
2022-03-14 10:32 ` Thomas Monjalon [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=44522398.fMDQidcC6G@thomas \
--to=thomas@monjalon.net \
--cc=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.