linux-kernel - Re: linux-next: build warning after merge of the powerpc tree

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] [day] [month] [year] [list]

Date: Thu, 16 May 2024 14:36:12 +1000
From: Stephen Rothwell <sfr@...hwell.id.au>
To: Michael Ellerman <mpe@...erman.id.au>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, PowerPC
 <linuxppc-dev@...ts.ozlabs.org>, Hari Bathini <hbathini@...ux.ibm.com>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the powerpc tree

Hi Michael,

On Thu, 16 May 2024 12:42:01 +1000 Michael Ellerman <mpe@...erman.id.au> wrote:
>
> Stephen Rothwell <sfr@...b.auug.org.au> writes:
> >
> > After merging the powerpc tree, today's (it may have been yesterday's)
> > linux-next build (powerpc allyesconfig) produced this warning:
> >
> > WARNING: modpost: vmlinux: section mismatch in reference: fadump_setup_param_area+0x200 (section: .text.fadump_setup_param_area) -> memblock_phys_alloc_range (section: .init.text)  
> 
> I don't see the warning, but clearly it is possible if the compiler
> decides not to inline fadump_setup_param_area().
> 
> What compiler version are you using?

$ gcc --version
gcc (Debian 13.2.0-7) 13.2.0

(on zz1 if you want to test)
-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped