Re: [REGRESSION] next/master: (build) use of undeclared identifier 'check_vector_unaligned_access'; did ...

On 7/30/26 18:59, KernelCI bot wrote:
> New build issue found on next/master:

Also reported by the "kernel test robot":
https://lore.kernel.org/oe-kbuild-all/[email protected]/

Fix is under review:

#regzbot introduced: f54d193db5da
#regzbot fix: riscv: unaligned: Fix check_vector_unaligned_access() stub
name
#regzbot monitor:
https://lore.kernel.org/all/[email protected]/
> ---
>  use of undeclared identifier 'check_vector_unaligned_access'; did you mean 'check_unaligned_access'? in arch/riscv/kernel/unaligned_access_speed.o (arch/riscv/kernel/unaligned_access_speed.c) [logspec:kbuild,kbuild.compiler.error]
> ---
> 
> Log excerpt:
> =====================================================
> /tmp/kci/linux/arch/riscv/kernel/unaligned_access_speed.c:380:24: error: use of undeclared identifier 'check_vector_unaligned_access'; did you mean 'check_unaligned_access'?
>   380 |                 schedule_on_each_cpu(check_vector_unaligned_access);
>       |                                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>       |                                      check_unaligned_access
> /tmp/kci/linux/arch/riscv/kernel/unaligned_access_speed.c:112:12: note: 'check_unaligned_access' declared here
>   112 | static int check_unaligned_access(struct page *page)
>       |            ^
> /tmp/kci/linux/arch/riscv/kernel/unaligned_access_speed.c:380:24: error: incompatible function pointer types passing 'int (struct page *)' to parameter of type 'work_func_t' (aka 'void (*)(struct work_struct *)') [-Wincompatible-function-pointer-types]
>   380 |                 schedule_on_each_cpu(check_vector_unaligned_access);
>       |                                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> /tmp/kci/linux/include/linux/workqueue.h:636:45: note: passing argument to parameter 'func' here
>   636 | extern int schedule_on_each_cpu(work_func_t func);
>       |                                             ^
> 2 errors generated.
> 
> =====================================================
> 
> When fixing this issue, please attribute this report according to the
> patch submission rules:
> 
> Reported-by: kernelci.org bot <[email protected]>
> Link: https://lore.kernel.org/all/[email protected]/
> 
> For complete logs and details about the environment used, see the issue
> on the KernelCI dashboard:
> 
> - dashboard: https://d.kernelci.org/i/maestro:93d4e1ca2f17ba7ce0541f3202fa21a0043a7f2c
> - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> - commit HEAD:  95d6a9ccef99117115e41e9adb271243bd5e985b
> - tags: next-20260730
> 
> # Builds where the incident occurred:
> 
> ## defconfig+allnoconfig on (riscv):
> - compiler: clang-21
> - config: None
> - dashboard: https://d.kernelci.org/build/maestro:6a6b7183798ea6c1ef929eaa
> 
> #regzbot introduced: 78bc8af4affb9a732504eb22eeac7d1e50883853..95d6a9ccef99117115e41e9adb271243bd5e985b
> #regzbot link: https://d.kernelci.org/i/maestro:93d4e1ca2f17ba7ce0541f3202fa21a0043a7f2c
> 
> #kernelci issue maestro:93d4e1ca2f17ba7ce0541f3202fa21a0043a7f2c
> 
> --
> This is an experimental report format. Please send feedback in!
> Talk to us at [email protected]
> 
> Made with love by the KernelCI team - https://kernelci.org
>