From: Akhil Goyal <akhil.goyal@nxp.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] aesni_mb: fix out-of-bounds access
Date: Tue, 18 Jun 2019 13:36:10 +0000 [thread overview]
Message-ID: <VE1PR04MB663936B495A13AF7062D2721E6EA0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190617143129.7106-1-roy.fan.zhang@intel.com>
Hi Fan,
>
> This patch fixes the out-of-bounds coverity issue by adding
> missed algorithms to the array.
>
> Coverity issue: 337683
>
> Fixes: c68d7aa354f6 ("crypto/aesni_mb: use architecture independent macros")
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h | 17
> ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h
> b/drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h
> index 4d439360f..dda78d989 100644
> --- a/drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h
> +++ b/drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h
> @@ -41,6 +41,14 @@ static const unsigned auth_blocksize[] = {
> [SHA_512] = 128,
> [AES_XCBC] = 16,
> [AES_CCM] = 16,
> + [AES_CMAC] = 16,
> + [AES_GMAC] = 16,
> + [AES_GCM] = 16,
> + [PLAIN_SHA1] = 64,
> + [PLAIN_SHA_224] = 64,
> + [PLAIN_SHA_256] = 64,
> + [PLAIN_SHA_384] = 128,
> + [PLAIN_SHA_512] = 128
> };
>
> /**
> @@ -65,7 +73,13 @@ static const unsigned
> auth_truncated_digest_byte_lengths[] = {
> [AES_XCBC] = 12,
> [AES_CMAC] = 12,
> [AES_CCM] = 8,
> - [NULL_HASH] = 0
> + [NULL_HASH] = 0,
> + [AES_GMAC] = 16,
> + [PLAIN_SHA1] = 20,
> + [PLAIN_SHA_224] = 28,
> + [PLAIN_SHA_256] = 32,
> + [PLAIN_SHA_384] = 48,
> + [PLAIN_SHA_512] = 64
> };
>
> /**
> @@ -90,6 +104,7 @@ static const unsigned auth_digest_byte_lengths[] = {
> [SHA_512] = 64,
> [AES_XCBC] = 16,
> [AES_CMAC] = 16,
> + [AES_CCM] = 16,
> [AES_GMAC] = 12,
> [NULL_HASH] = 0,
> [PLAIN_SHA1] = 20,
> --
> 2.14.5
Patchworks say that there is a compilation issue in this patch.
Could you please check.
Thanks,
Akhil
next prev parent reply other threads:[~2019-06-18 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 15:32 [dpdk-dev] [PATCH] " Fan Zhang
2019-05-15 15:32 ` Fan Zhang
2019-06-17 10:40 ` De Lara Guarch, Pablo
2019-06-17 14:31 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2019-06-18 13:36 ` Akhil Goyal [this message]
2019-06-18 16:34 ` De Lara Guarch, Pablo
2019-06-24 15:40 ` [dpdk-dev] [PATCH v3] " Fan Zhang
2019-06-25 12:47 ` 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=VE1PR04MB663936B495A13AF7062D2721E6EA0@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--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).