DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tejasree Kondoj <ktejasree@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
	Ankur Dwivedi <adwivedi@marvell.com>, <dev@dpdk.org>
Subject: [PATCH 1/4] crypto/cnxk: fix CMAC IV
Date: Fri, 17 Jun 2022 13:06:01 +0530	[thread overview]
Message-ID: <20220617073604.889403-2-ktejasree@marvell.com> (raw)
In-Reply-To: <20220617073604.889403-1-ktejasree@marvell.com>

Fixing CMAC IV length to 16 bytes.

Fixes: 759b5e653580 ("crypto/cnxk: support AES-CMAC")

Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
---
 drivers/crypto/cnxk/cnxk_se.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/crypto/cnxk/cnxk_se.h b/drivers/crypto/cnxk/cnxk_se.h
index 8ed3a8b2ef..cca44f1d3e 100644
--- a/drivers/crypto/cnxk/cnxk_se.h
+++ b/drivers/crypto/cnxk/cnxk_se.h
@@ -82,7 +82,7 @@ pdcp_iv_copy(uint8_t *iv_d, uint8_t *iv_s, const uint8_t pdcp_alg_type,
 			memcpy(iv_d, iv_s, 16);
 	} else {
 		/* AES-CMAC EIA2, microcode expects 16B zeroized IV */
-		for (j = 0; j < 4; j++)
+		for (j = 0; j < 16; j++)
 			iv_d[j] = 0;
 	}
 }
-- 
2.25.1


  reply	other threads:[~2022-06-17  7:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  7:36 [PATCH 0/4] support stream cipher chained operations Tejasree Kondoj
2022-06-17  7:36 ` Tejasree Kondoj [this message]
2022-06-17  7:36 ` [PATCH 2/4] crypto/cnxk: " Tejasree Kondoj
2022-06-17  7:36 ` [PATCH 3/4] crypto/cnxk: support scatter gather mode Tejasree Kondoj
2022-06-17  7:36 ` [PATCH 4/4] app/test: add additional stream cipher tests Tejasree Kondoj
2022-06-20 12:30   ` [PATCH v2] " Tejasree Kondoj
2022-06-21 12:51     ` Akhil Goyal
2022-06-21 14:27       ` Power, Ciara
2022-06-23  6:19         ` Tejasree Kondoj
2022-06-23 13:41     ` [PATCH v3] " Tejasree Kondoj
2022-06-23 18:19       ` [PATCH v4] " Tejasree Kondoj
2022-06-28 12:07         ` Power, Ciara
2022-06-28 12:15           ` 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=20220617073604.889403-2-ktejasree@marvell.com \
    --to=ktejasree@marvell.com \
    --cc=adwivedi@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@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).