From: Rui Wang <rui.y.wang@intel.com>
To: herbert@gondor.apana.org.au
Cc: tim.c.chen@linux.intel.com, rui.y.wang@intel.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] Fix sha1_mb failure and testing import()/export()
Date: Wed, 27 Jan 2016 17:08:34 +0800 [thread overview]
Message-ID: <1453885718-24599-1-git-send-email-rui.y.wang@intel.com> (raw)
Hi All,
This patchset resulted from the failure when loading sha1_mb. It
is because ahash drivers are now required to implement import()
and export(). Also, now it seems beneficial to add a test case in
testmgr to test import()/export(), thus:
patch01 - patch03 fix the problems while loading sha1_mb.
patch04 adds a test case for import() and export(). A hash algo's
import()/export() can be tested by simply adding .partial = 1 to
its corresponding struct hash_testvec where .np > 1.
v2: Leverage template[i].np in the test case as suggested by Tim Chen.
Rui Wang (4):
crypto x86/sha1_mb: Fix load failure
crypto: mcryptd - Fix load failure
crypto: algif_hash - wait for crypto_ahash_init() to complete
crypto: testmgr - Add a test case for import()/export()
arch/x86/crypto/sha-mb/sha1_mb.c | 39 +++++++++++
crypto/algif_hash.c | 4 +-
crypto/mcryptd.c | 1 +
crypto/testmgr.c | 136 +++++++++++++++++++++++++++++++++++++++
crypto/testmgr.h | 4 +-
5 files changed, 182 insertions(+), 2 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-01-27 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 9:08 Rui Wang [this message]
2016-01-27 9:08 ` [PATCH v2 1/4] crypto x86/sha1_mb: Fix load failure Rui Wang
2016-02-01 8:17 ` Herbert Xu
2016-01-27 9:08 ` [PATCH v2 2/4] crypto: mcryptd - " Rui Wang
2016-02-01 8:16 ` Herbert Xu
2016-01-27 9:08 ` [PATCH v2 3/4] crypto: algif_hash - wait for crypto_ahash_init() to complete Rui Wang
2016-02-01 8:17 ` Herbert Xu
2016-01-27 9:08 ` [PATCH v2 4/4] crypto: testmgr - Add a test case for import()/export() Rui Wang
2016-02-01 8:21 ` 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=1453885718-24599-1-git-send-email-rui.y.wang@intel.com \
--to=rui.y.wang@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@linux.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®