lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231204150807.600c2f09@canb.auug.org.au>
Date:   Mon, 4 Dec 2023 15:08:07 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Uros Bizjak <ubizjak@...il.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the tip tree

Hi Uros,

On Fri, 1 Dec 2023 13:09:45 +0100 Uros Bizjak <ubizjak@...il.com> wrote:
>
> On Fri, Dec 1, 2023 at 1:29 AM Stephen Rothwell <sfr@...b.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.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ