Re: linux-next: build warnings after merge of the tip tree

Uros Bizjak
2023-12-04T07:03:12Z

On Mon, Dec 4, 2023 at 5:08 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Uros,
>
> On Fri, 1 Dec 2023 13:09:45 +0100 Uros Bizjak <ubizjak@gmail.com> wrote:
> >
> > On Fri, Dec 1, 2023 at 1:29 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
> > > produced these warnings:
> > >
> > > WARNING: modpost: EXPORT symbol "const_pcpu_hot" [vmlinux] version generation failed, symbol will not be versioned.
> > > Is "const_pcpu_hot" prototyped in <asm/asm-prototypes.h>?
> > > WARNING: modpost: "const_pcpu_hot" [arch/x86/kernel/msr.ko] has no CRC!
> > > WARNING: modpost: "const_pcpu_hot" [arch/x86/kvm/kvm.ko] has no CRC!
> >
> > My build doesn't produce any warnings. A defconfig + enabling kvm.ko as module:
> >
> > ...
> > AR built-in.a
> > AR vmlinux.a
> > LD vmlinux.o
> > OBJCOPY modules.builtin.modinfo
> > GEN modules.builtin
> > MODPOST Module.symvers
> > CC .vmlinux.export.o
> > CC [M] arch/x86/kvm/kvm.mod.o
> > CC [M] fs/efivarfs/efivarfs.mod.o
> > ...
> >
> > Does the attached patch help? Or is there anything else I should do to
> > trigger the above problem?
>
> The patch does not help. I am just doing an X86_64 allmodconfig build
> with CONFIG_WERROR=n. gcc is
>
> $ x86_64-linux-gnu-gcc --version
> x86_64-linux-gnu-gcc (Debian 13.2.0-2) 13.2.0
>
> This is a cross build with a ppc64le host.

The warning is triggered by CONFIG_MODVERSIONS=y and will be fixed in
a different way by the patch in [1].

[1] https://lore.kernel.org/lkml/20231203232017.994963-1-ubizjak@gmail.com/

Thanks,
Uros.