#!/bin/bash
(perf record -e raw_syscalls:sys_enter $@ || \
perf record -e syscalls:sys_enter $@) 2> /dev/null
ttps://universe.0xinfinity.dev/distro/kernel/'/>
2025-08-27T15:15:35Zlib/crypto: Drop inline from all *_mod_init_arch() functions2025-08-27T15:15:35ZEric Biggersebiggers@kernel.org2025-08-16T02:04:57Zurn:sha1:5012bd2dc6ab0c4499923b3b6c6113def9b0c88b
Drop 'inline' from all the *_mod_init_arch() functions so that the
compiler will warn about any bugs where they are unused due to not being
wired up properly. (There are no such bugs currently, so this just
establishes a more robust convention for the future. Of course, these
functions also tend to get inlined anyway, regardless of the keyword.)
Link: https://lore.kernel.org/r/20250816020457.432040-1-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@kernel.org>
lib/crypto: arm/sha1: Migrate optimized code into library2025-07-14T18:11:29ZEric Biggersebiggers@kernel.org2025-07-12T23:22:58Zurn:sha1:70cb6ca58fddb02e269fe743ba75d53d577b5b1c
Instead of exposing the arm-optimized SHA-1 code via arm-specific
crypto_shash algorithms, instead just implement the sha1_blocks()
library function. This is much simpler, it makes the SHA-1 library
functions be arm-optimized, and it fixes the longstanding issue where
the arm-optimized SHA-1 code was disabled by default. SHA-1 still
remains available through crypto_shash, but individual architectures no
longer need to handle it.
To match sha1_blocks(), change the type of the nblocks parameter of the
assembly functions from int to size_t. The assembly functions actually
already treated it as size_t.
Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Link: https://lore.kernel.org/r/20250712232329.818226-8-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@kernel.org>