From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: stable@dpdk.org
Cc: pablo.de.lara.guarch@intel.com,
Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-stable] [PATCH] crypto/qat: fix aad capabilities for AES-GCM
Date: Fri, 12 May 2017 16:41:33 +0100 [thread overview]
Message-ID: <1494603694-5389-1-git-send-email-arkadiuszx.kusztal@intel.com> (raw)
From: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Fix aad capabilities for AES-GCM authtentication, aad is changed
from range 8-12 to 0-240
Fixes: 1703e94ac5ce ("qat: add driver for QuickAssist devices")
[ backported from upstream commit 87516a8f918a4fa59e365983dd82c107c5073d50]
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
---
drivers/crypto/qat/qat_crypto.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/crypto/qat/qat_crypto.c b/drivers/crypto/qat/qat_crypto.c
index 798cd98..1611bca 100644
--- a/drivers/crypto/qat/qat_crypto.c
+++ b/drivers/crypto/qat/qat_crypto.c
@@ -233,9 +233,9 @@ static const struct rte_cryptodev_capabilities qat_pmd_capabilities[] = {
.increment = 4
},
.aad_size = {
- .min = 8,
- .max = 12,
- .increment = 4
+ .min = 0,
+ .max = 240,
+ .increment = 1
}
}, }
}, }
--
2.1.0
next reply other threads:[~2017-05-12 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 15:41 Arek Kusztal [this message]
2017-05-12 15:41 ` [dpdk-stable] [PATCH] crypto/qat: fix segmentation fault in session create Arek Kusztal
[not found] <1493131274-21892-1-git-send-email-arkadiuszx.kusztal@intel.com>
[not found] ` <348A99DA5F5B7549AA880327E580B435891E90A8@IRSMSX101.ger.corp.intel.com>
2017-04-26 14:13 ` [dpdk-stable] [PATCH] crypto/qat: fix aad capabilities for AES-GCM De Lara Guarch, Pablo
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=1494603694-5389-1-git-send-email-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=pablo.de.lara.guarch@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).