From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
kunit-dev@googlegroups.com, Ard Biesheuvel <ardb@kernel.org>,
Rakuram Eswaran <rakuram.e96@gmail.com>
Subject: [GIT PULL] CRC updates for 6.18
Date: Sat, 27 Sep 2025 12:52:57 -0700 [thread overview]
Message-ID: <20250927195257.GA9798@quark> (raw)
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git tags/crc-for-linus
for you to fetch changes up to 136d029662cdde77d3e4db5c07de655f35f0239f:
Documentation/staging: Fix typo and incorrect citation in crc32.rst (2025-08-20 23:53:32 -0400)
----------------------------------------------------------------
Update crc_kunit to test the CRC functions in softirq and hardirq
contexts, similar to what the lib/crypto/ KUnit tests do. Move the
helper function needed to do this into a common header.
This is useful mainly to test fallback code paths for when
FPU/SIMD/vector registers are unusable.
----------------------------------------------------------------
Eric Biggers (4):
kunit, lib/crypto: Move run_irq_test() to common header
lib/crc: crc_kunit: Test CRC computation in interrupt contexts
lib/crc: Use underlying functions instead of crypto_simd_usable()
lib/crc: Drop inline from all *_mod_init_arch() functions
Rakuram Eswaran (1):
Documentation/staging: Fix typo and incorrect citation in crc32.rst
Documentation/staging/crc32.rst | 4 +-
include/kunit/run-in-irq-context.h | 129 ++++++++++++++++++++++++++++++++++
lib/crc/arm/crc-t10dif.h | 8 +--
lib/crc/arm/crc32.h | 8 +--
lib/crc/arm64/crc-t10dif.h | 8 +--
lib/crc/arm64/crc32.h | 11 +--
lib/crc/loongarch/crc32.h | 2 +-
lib/crc/mips/crc32.h | 2 +-
lib/crc/powerpc/crc-t10dif.h | 7 +-
lib/crc/powerpc/crc32.h | 7 +-
lib/crc/sparc/crc32.h | 2 +-
lib/crc/tests/crc_kunit.c | 62 +++++++++++++---
lib/crc/x86/crc-pclmul-template.h | 3 +-
lib/crc/x86/crc-t10dif.h | 2 +-
lib/crc/x86/crc32.h | 4 +-
lib/crc/x86/crc64.h | 2 +-
lib/crypto/tests/hash-test-template.h | 123 ++------------------------------
17 files changed, 219 insertions(+), 165 deletions(-)
create mode 100644 include/kunit/run-in-irq-context.h
next reply other threads:[~2025-09-27 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 19:52 Eric Biggers [this message]
2025-09-29 23:22 ` [GIT PULL] CRC updates for 6.18 pr-tracker-bot
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=20250927195257.GA9798@quark \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rakuram.e96@gmail.com \
--cc=torvalds@linux-foundation.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