From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: Ofir Drang <ofir.drang@arm.com>, Hadar Gat <hadar.gat@arm.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/6] crypto: fixes and cleanups
Date: Sun, 1 Jul 2018 08:02:33 +0100 [thread overview]
Message-ID: <1530428560-4440-1-git-send-email-gilad@benyossef.com> (raw)
The patch set fixes ccree IV handling, finup() operation (provided
by Hadar Gat) and CTS-AES mode of operation along a code cleanup.
Since our finup() method was obviously broken but was not detected
by testmgr, I've added finup() test to testmgr to catch it next
time it happened.
Changes from v1:
- Add missing "static" qualifier reported by kbuild bot
- Add CTS-AES fix and some more cleanups
Gilad Ben-Yossef (5):
crypto: testmgr: add hash finup tests
crypto: ccree: fix iv handling
crypto: ccree: remove dead legacy code
crypto: ccree: use CBC-CS3 CTS mode
crypto: ccree: rate limit debug print
Hadar Gat (1):
crypto: ccree: fix finup
crypto/testmgr.c | 55 +++++++++++++---
drivers/crypto/ccree/cc_cipher.c | 137 +++++++++++++++++++++++++--------------
drivers/crypto/ccree/cc_driver.c | 4 +-
drivers/crypto/ccree/cc_hash.c | 81 +++++------------------
4 files changed, 153 insertions(+), 124 deletions(-)
--
2.7.4
next reply other threads:[~2018-07-01 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 7:02 Gilad Ben-Yossef [this message]
2018-07-01 7:02 ` [PATCH v2 1/6] crypto: ccree: fix finup Gilad Ben-Yossef
2018-07-01 7:02 ` [PATCH v2 2/6] crypto: testmgr: add hash finup tests Gilad Ben-Yossef
2018-07-01 7:02 ` [PATCH v2 3/6] crypto: ccree: fix iv handling Gilad Ben-Yossef
2018-07-01 7:02 ` [PATCH v2 4/6] crypto: ccree: remove dead legacy code Gilad Ben-Yossef
2018-07-01 7:02 ` [PATCH v2 5/6] crypto: ccree: use CBC-CS3 CTS mode Gilad Ben-Yossef
2018-07-01 7:02 ` [PATCH v2 6/6] crypto: ccree: rate limit debug print Gilad Ben-Yossef
2018-07-02 12:58 ` Geert Uytterhoeven
2018-07-08 16:46 ` [PATCH v2 0/6] crypto: fixes and cleanups 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=1530428560-4440-1-git-send-email-gilad@benyossef.com \
--to=gilad@benyossef.com \
--cc=davem@davemloft.net \
--cc=hadar.gat@arm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ofir.drang@arm.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).