linux-kernel - Re: linux-next: build warning after merge of the ftrace 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20211025151327.00af129d9f876e252b042d01@kernel.org>
Date:   Mon, 25 Oct 2021 15:13:27 +0900
From:   Masami Hiramatsu <mhiramat@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        Masami Hiramatsu <mhiramat@...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 warning after merge of the ftrace tree

On Mon, 25 Oct 2021 15:39:42 +1100
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi all,
> 
> After merging the ftrace tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
> 
> WARNING: modpost: vmlinux.o(.text.unlikely+0x90082): Section mismatch in reference from the function xbc_alloc_mem() to the function .init.text:memblock_alloc_try_nid()
> The function xbc_alloc_mem() references
> the function __init memblock_alloc_try_nid().
> This is often because xbc_alloc_mem lacks a __init 
> annotation or the annotation of memblock_alloc_try_nid is wrong.
> 
> Introduced by commit
> 
>   4ee1b4cac236 ("bootconfig: Cleanup dummy headers in tools/bootconfig")

Thanks for reporting!
Let me fix that.



> 
> -- 
> Cheers,
> Stephen Rothwell


-- 
Masami Hiramatsu <mhiramat@...nel.org>