[PW_SID:1096320] [01/18] raid6: turn the userspace test harness into a kunit test by linux-riscv-bot · Pull Request #1959 · linux-riscv/linux

linux-riscv-bot · 2026-05-18T06:46:02Z

PR for series 1096320 applied to workflow__riscv__fixes

Name: [01/18] raid6: turn the userspace test harness into a kunit test
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=1096320
Version: 1

Currently the raid6 code can be compiled as userspace code to run the test suite. Convert that to be a kunit case with minimal changes to avoid mutating global state so that we can drop this requirement. Note that this is not a good kunit test case yet and will need a lot more work, but that is deferred until the raid6 code is moved to it's new place, which is easier if the userspace makefile doesn't need adjustments for the new location first. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

With the test code ported to kernel space, none of this is required. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Move the raid6 code to live in lib/raid/ with the XOR code, and change the internal organization so that each architecture has a subdirectory similar to the CRC, crypto and XOR libraries, and fix up the Makefile to only build files actually needed. Also move the kunit test case from the history test/ subdirectory to tests/ and use the normal naming scheme for it. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

These are not used anywhere in the kernel. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Just open code it as in other places in the kernel. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Stop directly calling into function pointers from users of the RAID6 PQ API, and provide exported functions with proper documentation and API guarantees asserts where applicable instead. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Quoting H. Peter Anvin who came up with the RAID6 P/Q algorithm, and who wrote the initial implementation, then still part of the md driver: The RAID-6 code has *never* supported only 3 units, and if it ever worked for *any* of the implementations it was purely by accident. Speaking as the original author I should know; this was deliberate as in some cases the degenerate case (3) would have required extra trays in the code to no user benefit. While md never allowed less than 4 devices, btrfs does. This new warning will trigger for such file systems, but given how it already causes havoc that is a good thing. If btrfs wants to fix third, it should switch to transparently use three-way mirroring underneath, which will work as P and Q are copies of the single data device by the definition of the Linux RAID 6 P/Q algorithm. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Split out two new headers from the public pq.h: - lib/raid/raid6/algos.h contains the algorithm lists private to lib/raid/raid6 - include/linux/raid/pq_tables.h contains the tables also used by async_tx providers. The public include/linux/pq.h is now limited to the public interface for the consumers of the RAID6 PQ API. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Replace the static array of algorithms with a call to an architecture helper to register algorithms. This serves two purposes: it avoid having to register all algorithms in a single central place, and it removes the need for the priority field by just registering the algorithms that the architecture considers suitable for the currently running CPUs. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Avoid indirect calls for P/Q parity generation. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Avoid expensive indirect calls for the recovery routines as well. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Drop the pointless mention of the file name, and use standard formatting for the top of file comments. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

The raid6 test combines various generation and recovery algorithms. Use KUNIT_CASE_PARAM and provide a generator that iterates over the possible combinations instead of looping inside a single test instance. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Use vmalloc for the data buffers instead of using static .data allocations. This provides for better out of bounds checking and avoids wasting kernel memory after the test has run. vmalloc is used instead of kmalloc to provide for better out of bounds access checking as in other kunit tests. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Move the global dataptr array into test_recover() as all sites that fill data or parity can use test_buffers directly, and this localized the override for the failed slots to the recovery testing routine. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

The current test has double-quadratic behavior in the selection for the updated ("XORed") disks, and in the selection of updated pointers, which makes scaling it to more tests difficult. At the same time it only ever tests with the maximum number of disks, which leaves a coverage hole for smaller ones. Fix this by randomizing the total number, failed disks and regions to update, and increasing the upper number of tests disks. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

Add code to add random alignment to the buffers to test the case where they are not page aligned, and to move the buffers to the end of the allocation so that they are next to the vmalloc guard page. This does not include the recovery buffers as the recovery requires page alignment. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

linux-riscv-bot · 2026-05-18T06:52:18Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 139.47 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T07:10:19Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1079.09 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T07:34:44Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1463.80 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T07:35:11Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 25.25 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T07:35:40Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 27.39 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T07:35:47Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 4.88 seconds
Result: WARNING
Output:

WARNING: please write a help paragraph that fully describes the config symbol with at least 4 lines
#58: FILE: lib/Kconfig:14:
+config RAID6_PQ_KUNIT_TEST
+	tristate "KUnit tests for RAID6 PQ functions" if !KUNIT_ALL_TESTS
+	depends on KUNIT
+	depends on RAID6_PQ
+	default KUNIT_ALL_TESTS
+	help
+	  Unit tests for the RAID6 PQ library functions.
+
+	  This is intended to help people writing architecture-specific
+	  optimized versions.  If unsure, say N.
+

WARNING: Prefer __aligned(PAGE_SIZE) over __attribute__((aligned(PAGE_SIZE)))
#366: FILE: lib/raid6/test/test.c:20:
+static char data[NDISKS][PAGE_SIZE] __attribute__((aligned(PAGE_SIZE)));

WARNING: Prefer __aligned(PAGE_SIZE) over __attribute__((aligned(PAGE_SIZE)))
#367: FILE: lib/raid6/test/test.c:21:
+static char recovi[PAGE_SIZE] __attribute__((aligned(PAGE_SIZE)));

WARNING: Prefer __aligned(PAGE_SIZE) over __attribute__((aligned(PAGE_SIZE)))
#368: FILE: lib/raid6/test/test.c:22:
+static char recovj[PAGE_SIZE] __attribute__((aligned(PAGE_SIZE)));

CHECK: Alignment should match open parenthesis
#395: FILE: lib/raid6/test/test.c:47:
+static void test_disks(struct kunit *test, const struct raid6_calls *calls,
+		const struct raid6_recov_calls *ra, int faila, int failb)

CHECK: Alignment should match open parenthesis
#447: FILE: lib/raid6/test/test.c:74:
+	KUNIT_EXPECT_MEMEQ_MSG(test, data[faila], recovi, PAGE_SIZE,
+		"algo=%-8s/%-8s faila miscompared: %3d[%c] (failb=%3d[%c])\n",

CHECK: Alignment should match open parenthesis
#452: FILE: lib/raid6/test/test.c:79:
+	KUNIT_EXPECT_MEMEQ_MSG(test, data[failb], recovj, PAGE_SIZE,
+		"algo=%-8s/%-8s failb miscompared: %3d[%c] (faila=%3d[%c])\n",

CHECK: Alignment should match open parenthesis
#525: FILE: lib/raid6/test/test.c:133:
+							test_disks(test, calls,
+									*ra, i, j);

CHECK: Please use a blank line after function/struct/union/enum declarations
#557: FILE: lib/raid6/test/test.c:157:
+};
+kunit_test_suite(raid6_test_suite);

total: 0 errors, 4 warnings, 5 checks, 458 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 fdee1f279c44 ("raid6: turn the userspace test harness into a kunit test") 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, 4 warnings, 5 checks, 458 lines checked
CHECK: Alignment should match open parenthesis
CHECK: Please use a blank line after function/struct/union/enum declarations
WARNING: Prefer __aligned(PAGE_SIZE) over __attribute__((aligned(PAGE_SIZE)))
WARNING: please write a help paragraph that fully describes the config symbol with at least 4 lines

linux-riscv-bot · 2026-05-18T07:37:15Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 87.19 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T07:37:17Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T07:37:23Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
kdoc
Desc: Detects for kdoc errors
Duration: 0.92 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T07:37:24Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
module-param
Desc: Detect module_param changes
Duration: 0.28 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T07:37:26Z

Patch 1: "[01/18] raid6: turn the userspace test harness into a kunit test"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.24 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T19:25:21Z

Patch 16: "[16/18] raid6_kunit: cleanup dataptr handling"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.23 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T19:25:23Z

Patch 16: "[16/18] raid6_kunit: cleanup dataptr handling"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.33 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T19:27:57Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 139.16 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T19:45:19Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1040.76 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:09:08Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1426.83 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:09:35Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 25.89 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:10:04Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 26.62 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:10:07Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 2.04 seconds
Result: WARNING
Output:

CHECK: Alignment should match open parenthesis
#100: FILE: lib/raid/raid6/tests/raid6_kunit.c:71:
+static void test_recover_one(struct kunit *test, unsigned int nr_buffers,
+		unsigned int len, int faila, int failb)

CHECK: Alignment should match open parenthesis
#166: FILE: lib/raid/raid6/tests/raid6_kunit.c:120:
+static void test_recover(struct kunit *test, unsigned int nr_buffers,
+		unsigned int len)

CHECK: Alignment should match open parenthesis
#197: FILE: lib/raid/raid6/tests/raid6_kunit.c:151:
+static void test_rmw_one(struct kunit *test, unsigned int nr_buffers,
+		unsigned int len, int p1, int p2)

CHECK: Alignment should match open parenthesis
#209: FILE: lib/raid/raid6/tests/raid6_kunit.c:162:
+static void test_rmw(struct kunit *test, unsigned int nr_buffers,
+		unsigned int len)

total: 0 errors, 0 warnings, 4 checks, 281 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 5f766dc64206 ("raid6_kunit: randomize parameters and increase limits") 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, 0 warnings, 4 checks, 281 lines checked
CHECK: Alignment should match open parenthesis

linux-riscv-bot · 2026-05-18T20:11:36Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 86.89 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:11:38Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.25 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:11:40Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
kdoc
Desc: Detects for kdoc errors
Duration: 0.88 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:11:42Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
module-param
Desc: Detect module_param changes
Duration: 0.27 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:11:44Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.23 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:11:46Z

Patch 17: "[17/18] raid6_kunit: randomize parameters and increase limits"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.33 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:14:19Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 139.51 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:31:44Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1042.51 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:55:35Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1429.79 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:56:03Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 25.60 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:56:31Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 27.07 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:56:36Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 3.85 seconds
Result: WARNING
Output:

CHECK: Alignment should match open parenthesis
#63: FILE: lib/raid/raid6/tests/raid6_kunit.c:115:
+	KUNIT_EXPECT_MEMEQ_MSG(test, aligned_buffers[faila], dataptrs[faila],
 			len,

CHECK: Alignment should match open parenthesis
#70: FILE: lib/raid/raid6/tests/raid6_kunit.c:121:
+	KUNIT_EXPECT_MEMEQ_MSG(test, aligned_buffers[failb], dataptrs[failb],
 			len,

total: 0 errors, 0 warnings, 2 checks, 89 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 570e060f8d37 ("raid6_kunit: randomize buffer alignment") 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, 0 warnings, 2 checks, 89 lines checked
CHECK: Alignment should match open parenthesis

linux-riscv-bot · 2026-05-18T20:58:05Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 86.59 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:58:07Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.24 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:58:09Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
kdoc
Desc: Detects for kdoc errors
Duration: 0.91 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:58:11Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
module-param
Desc: Detect module_param changes
Duration: 0.26 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:58:13Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.23 seconds
Result: PASS

linux-riscv-bot · 2026-05-18T20:58:15Z

Patch 18: "[18/18] raid6_kunit: randomize buffer alignment"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.31 seconds
Result: PASS

Linux RISC-V bot and others added 19 commits May 14, 2026 08:49

Adding CI files

cd9d421

raid6: use named initializers for struct raid6_calls

8b14a1b

Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Ard Biesheuvel <ardb@kernel.org> # kunit only on arm64 Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>

linux-riscv-bot force-pushed the workflow__riscv__fixes branch 2 times, most recently from a1231b7 to c03cdce Compare May 23, 2026 03:29

linux-riscv-bot closed this May 26, 2026

linux-riscv-bot deleted the pw1096320 branch May 26, 2026 00:04

Conversation

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

linux-riscv-bot commented May 18, 2026

Uh oh!

Reviewers

Assignees

Labels