From: Ard Biesheuvel <ardb+git@google.com>
To: linux-crypto@vger.kernel.org
Cc: ebiggers@kernel.org, herbert@gondor.apana.org.au,
Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH 0/2] crypto: Enable fuzz testing for generic crc32/crc32c
Date: Tue, 15 Oct 2024 16:15:15 +0200 [thread overview]
Message-ID: <20241015141514.3000757-4-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
crc32-generic and crc32c-generic are built around the architecture
library code for CRC-32, and the lack of distinct drivers for this arch
code means they are lacking test coverage.
Fix this by providing another, truly generic driver built on top of the
generic C code when fuzz testing is enabled.
Ard Biesheuvel (2):
crypto/crc32: Provide crc32-base alias to enable fuzz testing
crypto/crc32c: Provide crc32c-base alias to enable fuzz testing
crypto/crc32_generic.c | 73 ++++++++++++++------
crypto/crc32c_generic.c | 72 +++++++++++++------
crypto/testmgr.c | 2 +
3 files changed, 103 insertions(+), 44 deletions(-)
--
2.47.0.rc1.288.g06298d1525-goog
next reply other threads:[~2024-10-15 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 14:15 Ard Biesheuvel [this message]
2024-10-15 14:15 ` [PATCH 1/2] crypto/crc32: Provide crc32-base alias to enable fuzz testing Ard Biesheuvel
2024-10-16 2:21 ` Eric Biggers
2024-10-18 23:55 ` kernel test robot
2024-10-15 14:15 ` [PATCH 2/2] crypto/crc32c: Provide crc32c-base " Ard Biesheuvel
2024-10-19 11:16 ` kernel test robot
2024-10-16 2:20 ` [PATCH 0/2] crypto: Enable fuzz testing for generic crc32/crc32c Eric Biggers
2024-10-16 4:15 ` 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=20241015141514.3000757-4-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).