From: Eric Biggers <ebiggers@kernel.org>
To: ltp@lists.linux.it
Cc: linux-crypto@vger.kernel.org
Subject: [PATCH 0/6] ltp: AF_ALG test helpers and a few regression tests
Date: Wed, 20 Feb 2019 21:30:20 -0800 [thread overview]
Message-ID: <20190221053026.18489-1-ebiggers@kernel.org> (raw)
Hello,
This series adds helper functions for testing AF_ALG (the userspace
interface to algorithms in the Linux kernel's crypto API) to the
Linux Test Project. It then adds a few sample regression tests.
I've had these patches sitting around for a while with the goal of also
writing some "real" tests that test for more than these specific bugs,
but haven't gotten around to it yet. And I now consider further
improving the in-kernel crypto self-tests to be a higher priority. But
I figured I'd send this out as-is in case people are interested in
having this merged, e.g. maybe other people want to add AF_ALG tests to
LTP too and the 'tst_af_alg' lib would be a good starting point.
Eric Biggers (6):
lib: add tst_af_alg lib
crypto/af_alg01: new regression test for hmac nesting bug
crypto/af_alg02: new regression test for salsa20 empty message bug
crypto/af_alg03: new regression test for rfc7539 hash alg validation
crypto/af_alg04: new regression test for vmac race conditions
crypto/af_alg05: new regression test for skcipher_walk error bug
configure.ac | 1 +
include/lapi/if_alg.h | 40 ++++++++
include/tst_af_alg.h | 136 ++++++++++++++++++++++++++
lib/tst_af_alg.c | 147 +++++++++++++++++++++++++++++
runtest/cve | 2 +
testcases/kernel/crypto/.gitignore | 5 +
testcases/kernel/crypto/af_alg01.c | 79 ++++++++++++++++
testcases/kernel/crypto/af_alg02.c | 29 ++++++
testcases/kernel/crypto/af_alg03.c | 31 ++++++
testcases/kernel/crypto/af_alg04.c | 56 +++++++++++
testcases/kernel/crypto/af_alg05.c | 43 +++++++++
11 files changed, 569 insertions(+)
create mode 100644 include/lapi/if_alg.h
create mode 100644 include/tst_af_alg.h
create mode 100644 lib/tst_af_alg.c
create mode 100644 testcases/kernel/crypto/af_alg01.c
create mode 100644 testcases/kernel/crypto/af_alg02.c
create mode 100644 testcases/kernel/crypto/af_alg03.c
create mode 100644 testcases/kernel/crypto/af_alg04.c
create mode 100644 testcases/kernel/crypto/af_alg05.c
--
2.20.1
next reply other threads:[~2019-02-21 5:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 5:30 Eric Biggers [this message]
2019-02-21 5:30 ` [PATCH 1/6] lib: add tst_af_alg lib Eric Biggers
2019-03-15 9:38 ` [LTP] " Petr Vorel
2019-02-21 5:30 ` [PATCH 2/6] crypto/af_alg01: new regression test for hmac nesting bug Eric Biggers
2019-03-15 9:43 ` [LTP] " Petr Vorel
2019-02-21 5:30 ` [PATCH 3/6] crypto/af_alg02: new regression test for salsa20 empty message bug Eric Biggers
2019-02-21 5:30 ` [PATCH 4/6] crypto/af_alg03: new regression test for rfc7539 hash alg validation Eric Biggers
2019-03-15 9:29 ` [LTP] " Petr Vorel
2019-03-15 16:13 ` Eric Biggers
2019-03-15 18:40 ` Petr Vorel
2019-03-15 19:49 ` Eric Biggers
2019-02-21 5:30 ` [PATCH 5/6] crypto/af_alg04: new regression test for vmac race conditions Eric Biggers
2019-02-21 5:30 ` [PATCH 6/6] crypto/af_alg05: new regression test for skcipher_walk error bug Eric Biggers
2019-03-15 0:11 ` [PATCH 0/6] ltp: AF_ALG test helpers and a few regression tests Eric Biggers
2019-03-15 9:45 ` [LTP] " Petr Vorel
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=20190221053026.18489-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=ltp@lists.linux.it \
/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).