Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8;
MIME-Version: 1.0
References: <20231201112918.294b40b1@canb.auug.org.au> <CAFULd4Yfh0=TkhoevuJP1kghP5VLFj2zP9av68_s2pez3n2iog@mail.gmail.com>
 <20231204150807.600c2f09@canb.auug.org.au> <CAFULd4Y4n4uGy-pTc0PD6+-OytzGZHeJTPZ_CPJDq7VM7ChRdA@mail.gmail.com>
 <20231211161946.2f151d13@canb.auug.org.au>
In-Reply-To: <20231211161946.2f151d13@canb.auug.org.au>
From:   Uros Bizjak <ubizjak@gmail.com>
Date:   Mon, 11 Dec 2023 08:06:37 +0100
Message-ID: <CAFULd4Ysr_UxiE=jXoXMuJpzdzunNS=03tL2D0V+3zyr5tod+Q@mail.gmail.com>
Subject: Re: linux-next: build warnings after merge of the tip tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>,
        "H. Peter Anvin" <hpa@zytor.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Ingo Molnar <mingo@kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Mon, Dec 11, 2023 at 6:19=E2=80=AFAM Stephen Rothwell <sfr@canb.auug.org=
.au> wrote:
>
> Hi all,
>
> On Mon, 4 Dec 2023 08:02:56 +0100 Uros Bizjak <ubizjak@gmail.com> wrote:
> >
> > On Mon, Dec 4, 2023 at 5:08=E2=80=AFAM Stephen Rothwell <sfr@canb.auug.=
org.au> wrote:
> > >
> > > On Fri, 1 Dec 2023 13:09:45 +0100 Uros Bizjak <ubizjak@gmail.com> wro=
te:
> > > >
> > > > On Fri, Dec 1, 2023 at 1:29=E2=80=AFAM Stephen Rothwell <sfr@canb.a=
uug.org.au> wrote:
> > > > >
> > >  > After merging the tip tree, today's linux-next build (x86_64 allmo=
dconfig)
> > > > > produced these warnings:
> > > > >
> > > > > WARNING: modpost: EXPORT symbol "const_pcpu_hot" [vmlinux] versio=
n 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 n=
o CRC!
> > > > > WARNING: modpost: "const_pcpu_hot" [arch/x86/kvm/kvm.ko] has no C=
RC!
> > > >
> > > > My build doesn't produce any warnings. A defconfig + enabling kvm.k=
o 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 buil=
d
> > > with CONFIG_WERROR=3Dn. 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@gmail.com/

Thanks,
Uros.