From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: clabbe.montjoie@gmail.com, davem@davemloft.net,
geert+renesas@glider.be, herbert@gondor.apana.org.au,
keescook@chromium.org, maxime.ripard@free-electrons.com,
thomas.lendacky@amd.com, ulf.hansson@linaro.org
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2] crypto: add precalculated hash for zero message length
Date: Tue, 20 Oct 2015 09:33:56 +0200 [thread overview]
Message-ID: <1445326444-11019-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.
Using those precalculated hash make some additionnal constify patch necessary.
Changes since v1:
- Added missing sha/md5 header in testmgr.h
- indented a block comment in CCP
- moved precalculated hash from header to .c files
Regards
next reply other threads:[~2015-10-20 7:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 7:33 LABBE Corentin [this message]
2015-10-20 7:33 ` [PATCH 1/8] crypto: hash: add zero length message hash for shax and md5 LABBE Corentin
2015-10-20 7:33 ` [PATCH 2/8] crypto: niagara: Use precalculated hash from headers LABBE Corentin
2015-11-17 9:51 ` Herbert Xu
2015-10-20 7:33 ` [PATCH 3/8] crypto: ccp: " LABBE Corentin
2015-10-22 18:18 ` Tom Lendacky
2015-10-20 7:34 ` [PATCH 4/8] crypto: ux500: " LABBE Corentin
2015-10-21 3:12 ` kbuild test robot
2015-10-20 7:34 ` [PATCH 5/8] crypto: akcipher: fix typos in include/crypto/akcipher.h LABBE Corentin
2015-10-20 7:57 ` Stephan Mueller
2015-10-20 7:34 ` [PATCH 6/8] crypto: akcipher: the key parameter must be const u8 * LABBE Corentin
2015-11-17 9:52 ` Herbert Xu
2015-10-20 7:34 ` [PATCH 7/8] crypto: testmgr: Constify tested key/iv/plaintext/digest LABBE Corentin
2015-10-20 7:34 ` [PATCH 8/8] crypto: testmgr: Use the xxx_zero_message_hash from headers LABBE Corentin
2015-11-17 9:56 ` 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=1445326444-11019-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=keescook@chromium.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=thomas.lendacky@amd.com \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®