On Mon, Dec 11, 2023 at 6:19 AM Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > > Hi all, > > On Mon, 4 Dec 2023 08:02:56 +0100 Uros Bizjak <ubizjak@xxxxxxxxx> wrote: > > > > On Mon, Dec 4, 2023 at 5:08 AM Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > > > > > > On Fri, 1 Dec 2023 13:09:45 +0100 Uros Bizjak <ubizjak@xxxxxxxxx> wrote: > > > > > > > > On Fri, Dec 1, 2023 at 1:29 AM Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> 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. > > I am still seeing the warnings ... The -v3 patch series that fixes this and the remaining sparse warnings sits unreviewed for a week at [1]. I don't know why it is not being considered. [1] https://lore.kernel.org/lkml/20231204210320.114429-1-ubizjak@xxxxxxxxx/ Thanks, Uros.
