From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: clabbe.montjoie@gmail.com, davem@davemloft.net,
geert+renesas@glider.be, herbert@gondor.apana.org.au,
luis@debethencourt.com, maxime.ripard@free-electrons.com,
thomas.lendacky@amd.com, vinod.koul@intel.com
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/4] crypto: add precalculated hash for zero message length
Date: Thu, 17 Dec 2015 13:45:38 +0100 [thread overview]
Message-ID: <1450356342-12971-1-git-send-email-clabbe.montjoie@gmail.com> (raw)
Hello
Some crypto drivers cannot process empty data message and so rely on
precalculated hash.
This patch series add precalculated hash in headers and
make the drivers use them.
Changes since v3
- Added missing Kconfig depends on SHA256
Changes since v2
- Added missing Kconfig depends on MD5/SHA1
Changes since v1
- Moved arrays from headers to c file and made them EXPORT.
LABBE Corentin (4):
crypto: hash: add zero length message hash for shax and md5
crypto: niagara: Use precalculated hash from headers
crypto: ccp: Use precalculated hash from headers
crypto: ux500: Use precalculated hash from headers
crypto/md5.c | 6 ++++++
crypto/sha1_generic.c | 7 +++++++
crypto/sha256_generic.c | 16 ++++++++++++++
drivers/crypto/Kconfig | 3 +++
drivers/crypto/ccp/Kconfig | 2 ++
drivers/crypto/ccp/ccp-ops.c | 39 +++++++----------------------------
drivers/crypto/n2_core.c | 33 ++++++-----------------------
drivers/crypto/ux500/Kconfig | 2 ++
drivers/crypto/ux500/hash/hash_core.c | 20 ++----------------
include/crypto/md5.h | 2 ++
include/crypto/sha.h | 6 ++++++
11 files changed, 60 insertions(+), 76 deletions(-)
--
2.4.10
next reply other threads:[~2015-12-17 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 12:45 LABBE Corentin [this message]
2015-12-17 12:45 ` [PATCH v4 1/4] crypto: hash: add zero length message hash for shax and md5 LABBE Corentin
2015-12-17 12:45 ` [PATCH v4 2/4] crypto: niagara: Use precalculated hash from headers LABBE Corentin
2015-12-17 12:45 ` [PATCH v4 3/4] crypto: ccp: " LABBE Corentin
2015-12-17 12:45 ` [PATCH v4 4/4] crypto: ux500: " LABBE Corentin
2015-12-22 13:23 ` [PATCH v4 0/4] crypto: add precalculated hash for zero message length 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=1450356342-12971-1-git-send-email-clabbe.montjoie@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis@debethencourt.com \
--cc=maxime.ripard@free-electrons.com \
--cc=thomas.lendacky@amd.com \
--cc=vinod.koul@intel.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®