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>,
	Vidya Sagar Velumuri <vvelumuri@marvell.com>, <dev@dpdk.org>
Subject: [PATCH 01/13] crypto/cnxk: fix length of AES-CMAC algo
Date: Wed, 19 Oct 2022 19:45:01 +0530	[thread overview]
Message-ID: <20221019141513.1969052-2-ktejasree@marvell.com> (raw)
In-Reply-To: <20221019141513.1969052-1-ktejasree@marvell.com>

AES-CMAC uses PDCP opcode. Length should be passed
in bits.

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

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

diff --git a/drivers/crypto/cnxk/cnxk_se.h b/drivers/crypto/cnxk/cnxk_se.h
index 54a78d0a5a..c92e2cca2f 100644
--- a/drivers/crypto/cnxk/cnxk_se.h
+++ b/drivers/crypto/cnxk/cnxk_se.h
@@ -1323,6 +1323,9 @@ cpt_pdcp_alg_prep(uint32_t req_flags, uint64_t d_offs, uint64_t d_lens,
 			auth_offset += iv_len;
 
 			inputlen = auth_offset + auth_data_len;
+
+			/* length should be in bits */
+			auth_data_len *= 8;
 		}
 
 		outputlen = mac_len;
-- 
2.25.1


       reply	other threads:[~2022-10-19 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221019141513.1969052-1-ktejasree@marvell.com>
2022-10-19 14:15 ` Tejasree Kondoj [this message]
2022-10-19 14:15 ` [PATCH 02/13] common/cnxk: set inplace bit of lookaside IPsec Tejasree Kondoj
2022-10-19 14:15 ` [PATCH 03/13] crypto/cnxk: change capabilities as per firmware Tejasree Kondoj
2022-10-19 14:15 ` [PATCH 04/13] common/cnxk: support 103XX CPT Tejasree Kondoj
2022-10-19 14:15 ` [PATCH 05/13] common/cnxk: support custom UDP port values Tejasree Kondoj
2022-10-19 14:15 ` [PATCH 06/13] crypto/cnxk: update rlen calculation for lookaside mode Tejasree Kondoj
2022-10-19 14:15 ` [PATCH 07/13] crypto/cnxk: add support for DES and MD5 Tejasree Kondoj

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=20221019141513.1969052-2-ktejasree@marvell.com \
    --to=ktejasree@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=vvelumuri@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).