[PW_SID:970621] SHA-512 library functions by linux-riscv-bot · Pull Request #504 · linux-riscv/linux

linux-riscv-bot · 2025-06-11T04:28:59Z

PR for series 970621 applied to workflow__riscv__fixes

Name: SHA-512 library functions
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=970621
Version: 1

Rename existing functions and structs in architecture-optimized SHA-512 code that had names conflicting with the upcoming library interface which will be added to <crypto/sha2.h>: sha384_init, sha512_init, sha512_update, sha384, and sha512. Note: all affected code will be superseded by later commits that migrate the arch-optimized SHA-512 code into the library. This commit simply keeps the kernel building for the initial introduction of the library. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add basic support for SHA-384 and SHA-512 to lib/crypto/. Various in-kernel users will be able to use this instead of the old-school crypto API, which is harder to use and has more overhead. The basic support added by this commit consists of the API and its documentation, backed by a C implementation of the algorithms. sha512_block_generic() is derived from crypto/sha512_generic.c. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Since HMAC support is commonly needed and is fairly simple, include it as a first-class citizen of the SHA-512 library. The API supports both incremental and one-shot computation, and either preparing the key ahead of time or just using a raw key. The implementation is much more streamlined than crypto/hmac.c. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add KUnit tests for the SHA-384 and SHA-512 library functions, including the corresponding HMAC support. Testing strategy: - Each SHA variant gets its own KUnit test suite, but a header is used to share most of the test code among the SHA variants. - Test against vectors generated by the Python hashlib and hmac modules. - Test incremental computation. - Test with a guard page to catch buffer overruns even in assembly code. - Test various overlap and alignment cases. - Compute hashes in task, softirq, and hardirq context in parallel, to verify that the functions work as expected in all contexts and that fallback code paths are exercised. - Test that the finalization functions zeroize their context. - Include benchmarks, guarded by a separate Kconfig option. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add KUnit tests for the SHA-224 and SHA-256 library functions, using the test template that was added by the previous commit. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

sha512_generic_block_fn() will no longer be available when the SHA-512 support in the old-school crypto API is changed to just wrap the SHA-512 library. Replace the use of sha512_generic_block_fn() in sha512-riscv64-glue.c with temporary code that uses the library's __sha512_update(). This is just a temporary workaround to keep the kernel building and functional at each commit; this code gets superseded when the RISC-V optimized SHA-512 is migrated to lib/crypto/ anyway. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

…ibrary Delete crypto/sha512_generic.c, which provided "generic" SHA-384 and SHA-512 crypto_shash algorithms. Replace it with crypto/sha512.c which provides SHA-384, SHA-512, HMAC-SHA384, and HMAC-SHA512 crypto_shash algorithms using the corresponding library functions. This is a prerequisite for migrating all the arch-optimized SHA-512 code (which is almost 3000 lines) to lib/crypto/ rather than duplicating it. Since the replacement crypto_shash algorithms are implemented using the (potentially arch-optimized) library functions, give them cra_driver_names ending with "-lib" rather than "-generic". Update crypto/testmgr.c and one odd driver to take this change in driver name into account. Besides these cases which are accounted for, there are no known cases where the cra_driver_name was being depended on. This change does mean that the abstract partial block handling code in crypto/shash.c, which got added in 6.16, no longer gets used. But that's fine; the library has to implement the partial block handling anyway, and it's better to do it in the library since the block size and other properties of the algorithm are all fixed at compile time there, resulting in more streamlined code. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Instead of exposing the arm-optimized SHA-512 code via arm-specific crypto_shash algorithms, instead just implement the sha512_blocks() library function. This is much simpler, it makes the SHA-512 (and SHA-384) library functions be arm-optimized, and it fixes the longstanding issue where the arm-optimized SHA-512 code was disabled by default. SHA-512 still remains available through crypto_shash, but individual architectures no longer need to handle it. To match sha512_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. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Instead of exposing the arm64-optimized SHA-512 code via arm64-specific crypto_shash algorithms, instead just implement the sha512_blocks() library function. This is much simpler, it makes the SHA-512 (and SHA-384) library functions be arm64-optimized, and it fixes the longstanding issue where the arm64-optimized SHA-512 code was disabled by default. SHA-512 still remains available through crypto_shash, but individual architectures no longer need to handle it. To match sha512_blocks(), change the type of the nblocks parameter of the assembly functions from int or 'unsigned int' to size_t. Update the ARMv8 CE assembly function accordingly. The scalar assembly function actually already treated it as size_t. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Since arch/mips/cavium-octeon/crypto/octeon-crypto.h is now needed outside of its directory, move it to arch/mips/include/asm/octeon/crypto.h so that it can be included as <asm/octeon/crypto.h>. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Instead of exposing the mips-optimized SHA-512 code via mips-specific crypto_shash algorithms, instead just implement the sha512_blocks() library function. This is much simpler, it makes the SHA-512 (and SHA-384) library functions be mips-optimized, and it fixes the longstanding issue where the mips-optimized SHA-512 code was disabled by default. SHA-512 still remains available through crypto_shash, but individual architectures no longer need to handle it. Note: to see the diff from arch/mips/cavium-octeon/crypto/octeon-sha512.c to lib/crypto/mips/sha512.h, view this commit with 'git show -M10'. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Instead of exposing the riscv-optimized SHA-512 code via riscv-specific crypto_shash algorithms, instead just implement the sha512_blocks() library function. This is much simpler, it makes the SHA-512 (and SHA-384) library functions be riscv-optimized, and it fixes the longstanding issue where the riscv-optimized SHA-512 code was disabled by default. SHA-512 still remains available through crypto_shash, but individual architectures no longer need to handle it. To match sha512_blocks(), change the type of the nblocks parameter of the assembly function from int to size_t. The assembly function actually already treated it as size_t. Note: to see the diff from arch/riscv/crypto/sha512-riscv64-glue.c to lib/crypto/riscv/sha512.h, view this commit with 'git show -M10'. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Instead of exposing the s390-optimized SHA-512 code via s390-specific crypto_shash algorithms, instead just implement the sha512_blocks() library function. This is much simpler, it makes the SHA-512 (and SHA-384) library functions be s390-optimized, and it fixes the longstanding issue where the s390-optimized SHA-512 code was disabled by default. SHA-512 still remains available through crypto_shash, but individual architectures no longer need to handle it. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Instead of exposing the sparc-optimized SHA-512 code via sparc-specific crypto_shash algorithms, instead just implement the sha512_blocks() library function. This is much simpler, it makes the SHA-512 (and SHA-384) library functions be sparc-optimized, and it fixes the longstanding issue where the sparc-optimized SHA-512 code was disabled by default. SHA-512 still remains available through crypto_shash, but individual architectures no longer need to handle it. To match sha512_blocks(), change the type of the nblocks parameter of the assembly function from int to size_t. The assembly function actually already treated it as size_t. Note: to see the diff from arch/sparc/crypto/sha512_glue.c to lib/crypto/sparc/sha512.h, view this commit with 'git show -M10'. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Instead of exposing the x86-optimized SHA-512 code via x86-specific crypto_shash algorithms, instead just implement the sha512_blocks() library function. This is much simpler, it makes the SHA-512 (and SHA-384) library functions be x86-optimized, and it fixes the longstanding issue where the x86-optimized SHA-512 code was disabled by default. SHA-512 still remains available through crypto_shash, but individual architectures no longer need to handle it. To match sha512_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. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

sha512_base.h is no longer used, so remove it. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

linux-riscv-bot · 2025-06-11T04:34:26Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 103.38 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T04:49:46Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 918.87 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:10:29Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1241.48 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:10:51Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.64 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:11:14Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 21.79 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:11:17Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 1.40 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:12:30Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 71.74 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:12:32Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.49 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:12:35Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
kdoc
Desc: Detects for kdoc errors
Duration: 0.87 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:12:36Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
module-param
Desc: Detect module_param changes
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:12:38Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.22 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:12:40Z

Patch 1: "[01/16] crypto: sha512 - rename conflicting symbols"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.30 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:14:37Z

Patch 2: "[02/16] lib/crypto/sha512: add support for SHA-384 and SHA-512"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 102.16 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T05:32:03Z

Patch 2: "[02/16] lib/crypto/sha512: add support for SHA-384 and SHA-512"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1044.28 seconds
Result: ERROR
Output:

Redirect to /build/tmp.RCOT4r2jcx and /build/tmp.XjSsV3rn9b
Tree base:
f0685ee7b2df8 ("crypto: sha512 - rename conflicting symbols")
Building the whole tree with the patch
Building the tree before the patch
Building the tree with the patch
New errors added:
--- /build/tmp.EJA0A39ozn	2025-06-11 05:31:53.128375634 +0000
+++ /build/tmp.gidHZBcRM6	2025-06-11 05:31:53.139375549 +0000
@@ -3995,0 +3996 @@
+      1 lib/crypto/sha512.c: warning: EXPORT_SYMBOL() is used, but #include <linux/export.h> is missing
Per-file breakdown
error/warning file pre:
error/warning file post:
pre: 5022 post: 5023



real	14m3.519s
user	530m3.889s
sys	101m57.677s

real	1m38.944s
user	10m21.824s
sys	3m25.294s

real	1m32.446s
user	3m33.512s
sys	2m34.243s

linux-riscv-bot · 2025-06-11T14:37:20Z

Patch 14: "[14/16] lib/crypto/sha512: migrate sparc-optimized SHA-512 code to library"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 71.15 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T14:37:23Z

Patch 14: "[14/16] lib/crypto/sha512: migrate sparc-optimized SHA-512 code to library"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 1.07 seconds
Result: ERROR
Output:

Detected static functions without inline keyword in header files:
+
+static __ro_after_init DEFINE_STATIC_KEY_FALSE(have_sha512_opcodes);
+
--
+
+static void sha512_blocks(struct sha512_block_state *state,
+			  const u8 *data, size_t nblocks)
Detected static functions without inline keyword in header files: 1

linux-riscv-bot · 2025-06-11T14:37:25Z

Patch 14: "[14/16] lib/crypto/sha512: migrate sparc-optimized SHA-512 code to library"
kdoc
Desc: Detects for kdoc errors
Duration: 0.90 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T14:37:27Z

Patch 14: "[14/16] lib/crypto/sha512: migrate sparc-optimized SHA-512 code to library"
module-param
Desc: Detect module_param changes
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T14:37:29Z

Patch 14: "[14/16] lib/crypto/sha512: migrate sparc-optimized SHA-512 code to library"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.22 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T14:37:30Z

Patch 14: "[14/16] lib/crypto/sha512: migrate sparc-optimized SHA-512 code to library"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.31 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T14:39:27Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 101.96 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T14:55:00Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 931.65 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:15:56Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1253.78 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:16:18Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.72 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:16:42Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 21.70 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:16:47Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 3.46 seconds
Result: WARNING
Output:

WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#33: 
 rename {arch/x86/crypto => lib/crypto/x86}/sha512-avx-asm.S (97%)

total: 0 errors, 1 warnings, 0 checks, 183 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Commit 7e95c943421b ("lib/crypto/sha512: migrate x86-optimized SHA-512 code to library") has style problems, please review.

NOTE: Ignored message types: ALLOC_SIZEOF_STRUCT CAMELCASE COMMIT_LOG_LONG_LINE GIT_COMMIT_ID MACRO_ARG_REUSE NO_AUTHOR_SIGN_OFF

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.
total: 0 errors, 1 warnings, 0 checks, 183 lines checked
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?

linux-riscv-bot · 2025-06-11T15:17:59Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 70.77 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:18:02Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 1.21 seconds
Result: ERROR
Output:

Detected static functions without inline keyword in header files:
+
+static void sha512_blocks(struct sha512_block_state *state,
+			  const u8 *data, size_t nblocks)
Detected static functions without inline keyword in header files: 1

linux-riscv-bot · 2025-06-11T15:18:05Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
kdoc
Desc: Detects for kdoc errors
Duration: 0.87 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:18:07Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
module-param
Desc: Detect module_param changes
Duration: 0.29 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:18:09Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.22 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:18:11Z

Patch 15: "[15/16] lib/crypto/sha512: migrate x86-optimized SHA-512 code to library"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.32 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:20:08Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 103.04 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:36:19Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 969.72 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:58:04Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1303.01 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:58:26Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 20.88 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:58:49Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 21.57 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T15:58:52Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 1.39 seconds
Result: WARNING
Output:

WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#16: 
deleted file mode 100644

total: 0 errors, 1 warnings, 0 checks, 0 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Commit 3186f06b25cb ("crypto: sha512 - remove sha512_base.h") has style problems, please review.

NOTE: Ignored message types: ALLOC_SIZEOF_STRUCT CAMELCASE COMMIT_LOG_LONG_LINE GIT_COMMIT_ID MACRO_ARG_REUSE NO_AUTHOR_SIGN_OFF

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.
total: 0 errors, 1 warnings, 0 checks, 0 lines checked
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?

linux-riscv-bot · 2025-06-11T16:00:05Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 70.97 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T16:00:06Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.24 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T16:00:10Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
kdoc
Desc: Detects for kdoc errors
Duration: 1.78 seconds
Result: ERROR
Output:

Checking the tree before the patch
Checking the tree with the patch
Error: Cannot find file include/crypto/sha512_base.h
Errors and warnings before: 0 this patch: 1
New warnings added
0a1
> Error: Cannot find file include/crypto/sha512_base.h
Per-file breakdown

linux-riscv-bot · 2025-06-11T16:00:12Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
module-param
Desc: Detect module_param changes
Duration: 0.25 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T16:00:14Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.22 seconds
Result: PASS

linux-riscv-bot · 2025-06-11T16:00:15Z

Patch 16: "[16/16] crypto: sha512 - remove sha512_base.h"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.31 seconds
Result: PASS

ebiggers added 16 commits June 11, 2025 04:28

crypto: sha512 - remove sha512_base.h

3186f06

sha512_base.h is no longer used, so remove it. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Conversation

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025

Uh oh!

linux-riscv-bot commented Jun 11, 2025