From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: linux-mm <linux-mm@kvack.org>, open list <linux-kernel@vger.kernel.org>
Cc: Song Liu <song@kernel.org>,
Muchun Song <songmuchun@bytedance.com>,
Christoph Hellwig <hch@lst.de>, Vlastimil Babka <vbabka@suse.cz>,
David Hildenbrand <david@redhat.com>,
Rik van Riel <riel@surriel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: page_alloc.c:(.init.text+0xa7c): undefined reference to `vmalloc_huge'
Date: Mon, 25 Apr 2022 13:40:23 +0530 [thread overview]
Message-ID: <CA+G9fYscb1y4a17Sf5G_Aibt+WuSf-ks_Qjw9tYFy=A4sjCEug@mail.gmail.com> (raw)
Linux mainline arm architecture tinyconfig and allnoconfig builds failed.
These builds have config mmu not set.
# CONFIG_MMU is not set
Regressions found on arm:
- arm-clang-14-tinyconfig
- arm-clang-nightly-tinyconfig
- arm-gcc-11-tinyconfig
- arm-clang-13-tinyconfig
- arm-gcc-11-allnoconfig
- arm-clang-14-allnoconfig
- arm-clang-nightly-allnoconfig
- arm-gcc-8-allnoconfig
- arm-clang-11-allnoconfig
- arm-clang-11-tinyconfig
- arm-gcc-9-allnoconfig
- arm-gcc-9-tinyconfig
- arm-gcc-10-allnoconfig
- arm-gcc-8-tinyconfig
- arm-gcc-10-tinyconfig
- arm-clang-12-allnoconfig
- arm-clang-12-tinyconfig
- arm-clang-13-allnoconfig
Build error:
------------
arm-linux-gnueabihf-ld: mm/page_alloc.o: in function `alloc_large_system_hash':
page_alloc.c:(.init.text+0xa7c): undefined reference to `vmalloc_huge'
make[1]: *** [Makefile:1158: vmlinux] Error 1
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
tuxmake --runtime podman --target-arch arm --toolchain gcc-11
--kconfig tinyconfig
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
--
Linaro LKFT
https://lkft.linaro.org
[1] https://builds.tuxbuild.com/28GNGapkjXsbIbRSnHoGILqmaFp/
next reply other threads:[~2022-04-25 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 8:10 Naresh Kamboju [this message]
2022-04-25 8:28 ` Linus Torvalds
2022-04-25 8:44 ` Naresh Kamboju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+G9fYscb1y4a17Sf5G_Aibt+WuSf-ks_Qjw9tYFy=A4sjCEug@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=song@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox