mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Antoine Tenart <antoine.tenart@bootlin.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: Antoine Tenart <antoine.tenart@bootlin.com>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	thomas.petazzoni@bootlin.com, maxime.chevallier@bootlin.com,
	gregory.clement@bootlin.com, miquel.raynal@bootlin.com,
	nadavh@marvell.com, igall@marvell.com
Subject: [PATCH 00/14] crypto: inside-secure - self-test fixes
Date: Mon, 27 May 2019 16:50:52 +0200	[thread overview]
Message-ID: <20190527145106.8693-1-antoine.tenart@bootlin.com> (raw)

Hello,

The crypto runtime self-tests were improved and thanks to this we
spotted new issues within the Inside Secure SafeXcel cryptographic
engine driver:
- Intermediate IV were not retrieved from the hardware nor copied to the
  quest IV buffer for cbc(aes/des).
- HMAC updates wasn't supported.
- We spotted issues with the use of the SG lists.
- There was an issue with the use of result buffers.

The series fixes all those issues, and includes other small changes
found while doing this work.

Thanks!
Antoine

Antoine Tenart (14):
  crypto: inside-secure - remove empty line
  crypto: inside-secure - move comment
  crypto: inside-secure - fix coding style for a condition
  crypto: inside-secure - remove useless check
  crypto: inside-secure - improve the result error format when displayed
  crypto: inside-secure - change returned error when a descriptor
    reports an error
  crypto: inside-secure - enable context reuse
  crypto: inside-secure - unify cache reset
  crypto: inside-secure - fix zeroing of the request in ahash_exit_inv
  crypto: inside-secure - fix queued len computation
  crypto: inside-secure - implement IV retrieval
  crypto: inside-secure - add support for HMAC updates
  crypto: inside-secure - fix use of the SG list
  crypto: inside-secure - do not rely on the hardware last bit for
    result descriptors

 drivers/crypto/inside-secure/safexcel.c       |  13 +-
 drivers/crypto/inside-secure/safexcel.h       |  17 ++-
 .../crypto/inside-secure/safexcel_cipher.c    | 116 +++++++++++-------
 drivers/crypto/inside-secure/safexcel_hash.c  |  92 ++++++++------
 drivers/crypto/inside-secure/safexcel_ring.c  |   3 +
 5 files changed, 157 insertions(+), 84 deletions(-)

-- 
2.21.0


             reply	other threads:[~2019-05-27 14:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 14:50 Antoine Tenart [this message]
2019-05-27 14:50 ` [PATCH 01/14] crypto: inside-secure - remove empty line Antoine Tenart
2019-05-27 14:50 ` [PATCH 02/14] crypto: inside-secure - move comment Antoine Tenart
2019-05-27 14:50 ` [PATCH 03/14] crypto: inside-secure - fix coding style for a condition Antoine Tenart
2019-05-27 14:50 ` [PATCH 04/14] crypto: inside-secure - remove useless check Antoine Tenart
2019-05-27 14:50 ` [PATCH 05/14] crypto: inside-secure - improve the result error format when displayed Antoine Tenart
2019-05-27 14:50 ` [PATCH 06/14] crypto: inside-secure - change returned error when a descriptor reports an error Antoine Tenart
2019-05-27 14:50 ` [PATCH 07/14] crypto: inside-secure - enable context reuse Antoine Tenart
2019-05-27 14:51 ` [PATCH 08/14] crypto: inside-secure - unify cache reset Antoine Tenart
2019-05-27 14:51 ` [PATCH 09/14] crypto: inside-secure - fix zeroing of the request in ahash_exit_inv Antoine Tenart
2019-05-27 14:51 ` [PATCH 10/14] crypto: inside-secure - fix queued len computation Antoine Tenart
2019-05-27 14:51 ` [PATCH 11/14] crypto: inside-secure - implement IV retrieval Antoine Tenart
2019-05-27 14:51 ` [PATCH 12/14] crypto: inside-secure - add support for HMAC updates Antoine Tenart
2019-05-27 14:51 ` [PATCH 13/14] crypto: inside-secure - fix use of the SG list Antoine Tenart
2019-05-27 14:51 ` [PATCH 14/14] crypto: inside-secure - do not rely on the hardware last bit for result descriptors Antoine Tenart
2019-06-06  6:50 ` [PATCH 00/14] crypto: inside-secure - self-test fixes 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=20190527145106.8693-1-antoine.tenart@bootlin.com \
    --to=antoine.tenart@bootlin.com \
    --cc=davem@davemloft.net \
    --cc=gregory.clement@bootlin.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=igall@marvell.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=nadavh@marvell.com \
    --cc=thomas.petazzoni@bootlin.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

all inboxes | Powered by JetHome®