linux-kernel - Re: linux-next: Tree for Oct 25 (bootconfig: xbc_alloc

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: <20211026161130.0d308f46@canb.auug.org.au>
Date:   Tue, 26 Oct 2021 16:11:30 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Steven Rostedt <rostedt@...dmis.org>
Subject: Re: linux-next: Tree for Oct 25 (bootconfig: xbc_alloc_mem())

Hi Randy,

On Mon, 25 Oct 2021 20:20:02 -0700 Randy Dunlap <rdunlap@...radead.org> wrote:
>
> on i386:
> 
> WARNING: modpost: vmlinux.o(.text.unlikely+0x29b16): 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.
> 
> Looks like lib/bootconfig.c::xbc_alloc_mem() should be marked
> as __init (when it's built for KERNEL).

See: https://lore.kernel.org/lkml/20211025153942.0c31bd06@canb.auug.org.au/

P.S. please trim your replies.
-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped