Re: [PATCH 5/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock()

[Thomas Weißschuh]

On Fri, Jun 19, 2026 at 04:11:21PM +0200, Nam Cao wrote:
(...)
> --- a/arch/riscv/kernel/vdso/Makefile
> +++ b/arch/riscv/kernel/vdso/Makefile
> @@ -27,12 +27,24 @@ asflags-y += -DVDSO_CFI=1
>  endif
>  
>  # Files to link into the vdso
> -obj-vdso = $(patsubst %, %.o, $(vdso-syms)) note.o
> +obj-vdso := $(patsubst %, %.o, $(vdso-syms)) note.o
>  
>  ifdef CONFIG_VDSO_GETRANDOM
>  obj-vdso += vgetrandom-chacha.o
>  endif
>  
> +ifdef CONFIG_FUTEX_ROBUST_UNLOCK
> +
> +obj-vdso += futex.o
> +
> +ifdef CONFIG_64BIT
> +vdso-syms += __vdso_futex_robust_list64_try_unlock
> +else
> +vdso-syms += __vdso_futex_robust_list32_try_unlock
> +endif
> +
> +endif
> +
>  ccflags-y := -fno-stack-protector
>  ccflags-y += -DDISABLE_BRANCH_PROFILING
>  ccflags-y += -fno-builtin

This is missing a

CFLAGS_REMOVE_futex.o = $(CC_FLAGS_FTRACE) $(CC_FLAGS_SCS)

Otherwise we get this:

https://lore.kernel.org/oe-kbuild-all/202606270658.zYkKDlzo-lkp@xxxxxxxxx/

Or add a preparatory commit which uses ccflags-remove-y instead of
listing all the objects manually.

(...)