From: Andrei Botila <andrei.botila@oss.nxp.com>
To: Horia Geanta <horia.geanta@nxp.com>,
Aymen Sghaier <aymen.sghaier@nxp.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 00/10] crypto: caam - xts(aes) updates
Date: Tue, 22 Sep 2020 19:03:18 +0300 [thread overview]
Message-ID: <20200922160328.28926-1-andrei.botila@oss.nxp.com> (raw)
From: Andrei Botila <andrei.botila@nxp.com>
This patch series fixes some problems in CAAM's implementation of xts(aes):
- CAAM until Era 9 can't process XTS with 16B IV
- CAAM can only process in hardware XTS key lengths of 16B and 32B
- These hardware limitations are resolved through a fallback
- CAAM used to return 0 for XTS block length equal to zero
This patch series also adds a new feature in CAAM's xts(aes):
- CAAM is now able to process XTS with 16B IV in HW
Changes since v2:
- modified xts_skcipher_ivsize() based on comments
- squashed the previous 7-9/12 commits
Changes since v1:
- use only get_unaligned() for calculating XTS IV size
- fixed the double calling of crypto_skcipher_set_reqsize() in case of XTS
- added a patch which modifies the return value for XTS when block length
is equal to zero
Andrei Botila (10):
crypto: caam/jr - add fallback for XTS with more than 8B IV
crypto: caam/qi - add fallback for XTS with more than 8B IV
crypto: caam/qi2 - add fallback for XTS with more than 8B IV
crypto: caam/jr - add support for more XTS key lengths
crypto: caam/qi - add support for more XTS key lengths
crypto: caam/qi2 - add support for more XTS key lengths
crypto: caam - add xts check for block length equal to zero
crypto: caam/jr - add support for XTS with 16B IV
crypto: caam/qi - add support for XTS with 16B IV
crypto: caam/qi2 - add support for XTS with 16B IV
drivers/crypto/caam/Kconfig | 3 +
drivers/crypto/caam/caamalg.c | 94 +++++++++++++++++++++---
drivers/crypto/caam/caamalg_desc.c | 27 ++++---
drivers/crypto/caam/caamalg_qi.c | 94 +++++++++++++++++++++---
drivers/crypto/caam/caamalg_qi2.c | 111 ++++++++++++++++++++++++++---
drivers/crypto/caam/caamalg_qi2.h | 2 +
6 files changed, 293 insertions(+), 38 deletions(-)
--
2.17.1
next reply other threads:[~2020-09-22 16:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 16:03 Andrei Botila [this message]
2020-09-22 16:03 ` [PATCH v3 01/10] crypto: caam/jr - add fallback for XTS with more than 8B IV Andrei Botila
2020-09-22 16:03 ` [PATCH v3 02/10] crypto: caam/qi " Andrei Botila
2020-09-22 16:03 ` [PATCH v3 03/10] crypto: caam/qi2 " Andrei Botila
2020-09-22 16:03 ` [PATCH v3 04/10] crypto: caam/jr - add support for more XTS key lengths Andrei Botila
2020-09-22 16:03 ` [PATCH v3 05/10] crypto: caam/qi " Andrei Botila
2020-09-22 16:03 ` [PATCH v3 06/10] crypto: caam/qi2 " Andrei Botila
2020-09-22 16:03 ` [PATCH v3 07/10] crypto: caam - add xts check for block length equal to zero Andrei Botila
2020-09-22 16:03 ` [PATCH v3 08/10] crypto: caam/jr - add support for XTS with 16B IV Andrei Botila
2020-09-22 16:03 ` [PATCH v3 09/10] crypto: caam/qi " Andrei Botila
2020-09-22 16:03 ` [PATCH v3 10/10] crypto: caam/qi2 " Andrei Botila
2020-09-23 11:59 ` [PATCH v3 00/10] crypto: caam - xts(aes) updates Horia Geantă
2020-10-02 11:54 ` Herbert Xu
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=20200922160328.28926-1-andrei.botila@oss.nxp.com \
--to=andrei.botila@oss.nxp.com \
--cc=aymen.sghaier@nxp.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.