From: Ard Biesheuvel <ardb+git@google.com>
To: linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au, ebiggers@kernel.org,
Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH v2 0/2] crypto: Enable fuzz testing for arch code
Date: Wed, 16 Oct 2024 20:57:23 +0200 [thread overview]
Message-ID: <20241016185722.400643-4-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
Follow-up to [0].
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 exposing the arch library code as a separate driver (with a
higher priority) if it is different from the generic C code. Update the
crc32-generic drivers to always use the generic C code.
Changes since [0]:
- make generic drivers truly generic, and expose the arch code as a
separate driver
[0] https://lore.kernel.org/all/20241015141514.3000757-4-ardb+git@google.com/T/#u
Ard Biesheuvel (2):
crypto/crc32: Provide crc32-arch driver for accelerated library code
crypto/crc32c: Provide crc32c-arch driver for accelerated library code
crypto/Makefile | 2 +
crypto/crc32_generic.c | 94 +++++++++++++++-----
crypto/crc32c_generic.c | 94 +++++++++++++++-----
lib/crc32.c | 4 +
4 files changed, 148 insertions(+), 46 deletions(-)
--
2.47.0.rc1.288.g06298d1525-goog
next reply other threads:[~2024-10-16 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 18:57 Ard Biesheuvel [this message]
2024-10-16 18:57 ` [PATCH v2 1/2] crypto/crc32: Provide crc32-arch driver for accelerated library code Ard Biesheuvel
2024-10-16 18:57 ` [PATCH v2 2/2] crypto/crc32c: Provide crc32c-arch " Ard Biesheuvel
2024-10-16 21:52 ` [PATCH v2 0/2] crypto: Enable fuzz testing for arch code Eric Biggers
2024-10-26 6:58 ` 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=20241016185722.400643-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.