linux-kernel - Re: arch/arm/mm/init.o: in function `arm_memblock_init': init.c:(.init.text+0xc8): undefined reference to `phys_initrd

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

Message-ID: <Yw899e/S6wuo4EX6@kernel.org>
Date:   Wed, 31 Aug 2022 13:54:45 +0300
From:   Mike Rapoport <rppt@...nel.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        open list <linux-kernel@...r.kernel.org>,
        Russell King <linux@...linux.org.uk>,
        Wang Kefeng <wangkefeng.wang@...wei.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>,
        Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
        Matija Glavinic Pecotic <matija.glavinic-pecotic.ext@...ia.com>,
        Victor Hassan <victor@...winnertech.com>
Subject: Re: arch/arm/mm/init.o: in function `arm_memblock_init':
 init.c:(.init.text+0xc8): undefined reference to `phys_initrd_start'

On Wed, Aug 31, 2022 at 02:26:36PM +0530, Naresh Kamboju wrote:
> The following arm builds failed on Linux next-20220831.
> 
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> 
> Regressions found on arm:
>    - build-clang-14-allnoconfig
>    - build-gcc-11-tinyconfig
>    - build-clang-11-tinyconfig
>    - build-gcc-9-tinyconfig
>    - build-gcc-11-orion5x_defconfig
>    - build-gcc-10-allnoconfig
>    - build-clang-nightly-orion5x_defconfig
>    - build-gcc-8-orion5x_defconfig
>    - build-clang-11-allnoconfig
>    - build-gcc-8-tinyconfig
>    - build-clang-11-orion5x_defconfig
>    - build-clang-nightly-tinyconfig
>    - build-clang-13-allnoconfig
>    - build-gcc-9-allnoconfig
>    - build-clang-13-tinyconfig
>    - build-clang-14-orion5x_defconfig
>    - build-clang-13-orion5x_defconfig
>    - build-clang-14-tinyconfig
>    - build-gcc-8-allnoconfig
>    - build-gcc-9-orion5x_defconfig
>    - build-clang-12-tinyconfig
>    - build-clang-nightly-allnoconfig
>    - build-gcc-10-orion5x_defconfig
>    - build-clang-12-orion5x_defconfig
>    - build-gcc-10-tinyconfig
>    - build-clang-12-allnoconfig
>    - build-gcc-11-allnoconfig
>    
> Build error:
> ------------
> arm-linux-gnueabihf-ld: arch/arm/mm/init.o: in function `arm_memblock_init':
> init.c:(.init.text+0xc8): undefined reference to `phys_initrd_start'
> make[1]: *** [/builds/linux/Makefile:1250: vmlinux] Error 1

Looks like this is because of 
Fixes: b35b2736b43d ("ARM: 9230/1: Support initrd with address in boot alias region")
that uses phys_initrd_start regardless of CONFIG_BLK_DEV_INITRD
 
> Build log link:
> https://builds.tuxbuild.com/2E6pMzczzw7tLMxz7WFjaPgQ9Io/
> 
> Steps to reproduce:
> -------------------
> # To install tuxmake on your system globally:
> # sudo pip3 install -U tuxmake
> 
> tuxmake --runtime podman --target-arch arm --toolchain gcc-11 --kconfig
> tinyconfig
> 
> --
> Linaro LKFT
> https://lkft.linaro.org

-- 
Sincerely yours,
Mike.