Re: linux-next: build failure after merge of the random tree

[Nathan Chancellor <nathan@kernel.org>]

On Thu, Oct 01, 2026 at 04:40:32PM +0100, Mark Brown wrote:
> Hi all,
> 
> After merging the random tree, today's linux-next build
> (arm64 defconfig) failed like this:
> 
> In file included from /tmp/next/build/include/linux/list.h:11,
>                  from /tmp/next/build/include/linux/resource_ext.h:9,
>                  from /tmp/next/build/include/linux/acpi.h:14,
>                  from /tmp/next/build/include/acpi/apei.h:9,
>                  from /tmp/next/build/include/acpi/ghes.h:5,
>                  from /tmp/next/build/include/linux/arm_sdei.h:8,
>                  from /tmp/next/build/arch/arm64/kernel/asm-offsets.c:11:
> /tmp/next/build/include/linux/objpool.h: In function
> '__objpool_try_get_slot': /tmp/next/build/include/linux/objpool.h:130:42:
> warning: taking address of packed member of 'struct objpool_slot' may
> result in an unaligned pointer value [-Waddress-of-packed-member]
>   130 |         uint32_t head = smp_load_acquire(&slot->head);
...
> and x86_64 allmodconfig had a similarly bad time with -Werror turned on.
> 
> Caused by commit
> 
>    56ff95ee85715 (random: vDSO: avoid call to memset() when zeroing reserved parameter)
> 
> (which is the only new commit in the random tree.)  I have used the
> version from next-20260930 instead.

Just to close the loop for others, I think this is a result of a
problematic resolution between the random and Kbuild trees, not a
problem with that change in and of itself.

  https://lore.kernel.org/20261001192731.GA713751@ax162/

-- 
Cheers,
Nathan