From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: stable@dpdk.org
Cc: fiona.trahe@intel.com, bluca@debian.org, ferruh.yigit@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-stable] [PATCH] crypto/qat: fix not included algs for zero counter
Date: Thu, 26 Sep 2019 10:06:53 +0200 [thread overview]
Message-ID: <20190926080653.5492-1-arkadiuszx.kusztal@intel.com> (raw)
Algorithms NULL, XCBC, CBC-MAC should have had zeroed counter.
Fixes: e25200fbb45d ("qat: add cipher/auth only")
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
This patch obsoletes patches:
http://patches.dpdk.org/patch/48715/
http://patches.dpdk.org/patch/48716/
drivers/crypto/qat/qat_adf/qat_algs_build_desc.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/crypto/qat/qat_adf/qat_algs_build_desc.c b/drivers/crypto/qat/qat_adf/qat_algs_build_desc.c
index b939381..192925e 100644
--- a/drivers/crypto/qat/qat_adf/qat_algs_build_desc.c
+++ b/drivers/crypto/qat/qat_adf/qat_algs_build_desc.c
@@ -751,7 +751,10 @@ int qat_alg_aead_session_create_content_desc_auth(struct qat_session *cdesc,
if (cdesc->qat_hash_alg == ICP_QAT_HW_AUTH_ALGO_SNOW_3G_UIA2
|| cdesc->qat_hash_alg == ICP_QAT_HW_AUTH_ALGO_KASUMI_F9
- || cdesc->qat_hash_alg == ICP_QAT_HW_AUTH_ALGO_ZUC_3G_128_EIA3)
+ || cdesc->qat_hash_alg == ICP_QAT_HW_AUTH_ALGO_ZUC_3G_128_EIA3
+ || cdesc->qat_hash_alg == ICP_QAT_HW_AUTH_ALGO_AES_XCBC_MAC
+ || cdesc->qat_hash_alg == ICP_QAT_HW_AUTH_ALGO_AES_CBC_MAC
+ || cdesc->qat_hash_alg == ICP_QAT_HW_AUTH_ALGO_NULL)
hash->auth_counter.counter = 0;
else {
int block_size = qat_hash_get_block_size(cdesc->qat_hash_alg);
--
2.1.0
next reply other threads:[~2019-09-26 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 8:06 Arek Kusztal [this message]
2019-09-26 8:18 ` Luca Boccassi
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=20190926080653.5492-1-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=bluca@debian.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@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 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).