From: Herbert Xu <herbert@gondor.apana.org.au>
To: Rabin Vincent <rabin.vincent@axis.com>
Cc: linux-crypto@vger.kernel.org, Rabin Vincent <rabinv@axis.com>
Subject: Re: [PATCH] crypto: tcrypt - Add mode to test specified algs
Date: Mon, 23 Jan 2017 22:14:03 +0800 [thread overview]
Message-ID: <20170123141403.GC19957@gondor.apana.org.au> (raw)
In-Reply-To: <1484756700-10019-1-git-send-email-rabin.vincent@axis.com>
On Wed, Jan 18, 2017 at 05:25:00PM +0100, Rabin Vincent wrote:
> From: Rabin Vincent <rabinv@axis.com>
>
> tcrypt offers a bunch of mode= values to test various (groups of)
> algorithms, but there is no way provided to test a subset of the
> algorithms. This adds a new mode=2000 which interprets alg= as a
> colon-separated list of algorithms to test with alg_test(). Colon is
> used since the names may contain commas.
>
> This is useful during driver development and also for regression testing
> to avoid the errors that are otherwise generated when attempting to test
> non-enabled algorithms.
>
> # insmod tcrypt.ko dyndbg mode=2000 alg="cbc(aes):ecb(aes):hmac(sha256):sha256:xts(aes)"
> [ 649.418569] tcrypt: testing cbc(aes)
> [ 649.420809] tcrypt: testing ecb(aes)
> [ 649.422627] tcrypt: testing hmac(sha256)
> [ 649.424861] tcrypt: testing sha256
> [ 649.426368] tcrypt: testing xts(aes)
> [ 649.430014] tcrypt: all tests passed
>
> Signed-off-by: Rabin Vincent <rabinv@axis.com>
You can already do this with the existing mode=0 setting, no?
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2017-01-23 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 16:25 [PATCH] crypto: tcrypt - Add mode to test specified algs Rabin Vincent
2017-01-23 14:14 ` Herbert Xu [this message]
2017-01-23 15:13 ` Rabin Vincent
2017-02-01 14:03 ` 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=20170123141403.GC19957@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=rabin.vincent@axis.com \
--cc=rabinv@axis.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).