From: <Conor.Dooley@microchip.com>
To: <lkp@intel.com>, <liushixin2@huawei.com>
Cc: <llvm@lists.linux.dev>, <kbuild-all@lists.01.org>, <linux-mm@kvack.org>
Subject: Re: [linux-next:master 9063/11993] ld.lld: error: undefined symbol: find_vm_area
Date: Sat, 1 Oct 2022 16:04:01 +0000 [thread overview]
Message-ID: <3a05c91e-c606-c90b-5d63-29a1df6105c9@microchip.com> (raw)
In-Reply-To: <202210012339.AsyuqYMl-lkp@intel.com>
On 01/10/2022 16:48, kernel test robot wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Hi Liu,
>
> FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 274d7803837da78dfc911bcda0d593412676fc20
> commit: d9729d9cdcd69ee2e9c9be4cc2230227f015ca9f [9063/11993] riscv: Enable HAVE_ARCH_HUGE_VMALLOC for 64BIT
> config: riscv-buildonly-randconfig-r001-20220926
> compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 791a7ae1ba3efd6bca96338e10ffde557ba83920)
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # install riscv cross compiling tool for clang build
> # apt-get install binutils-riscv64-linux-gnu
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=d9729d9cdcd69ee2e9c9be4cc2230227f015ca9f
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout d9729d9cdcd69ee2e9c9be4cc2230227f015ca9f
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
These should *not* be in my -next & I apologise for applying them accidentally.
Now dropped!
>
>>> ld.lld: error: undefined symbol: find_vm_area
> >>> referenced by page_alloc.c:2303 (mm/page_alloc.c:2303)
> >>> page_alloc.o:(alloc_large_system_hash) in archive mm/built-in.a
>
> Kconfig warnings: (for reference only)
> WARNING: unmet direct dependencies detected for HAVE_ARCH_HUGE_VMALLOC
> Depends on [n]: HAVE_ARCH_HUGE_VMAP [=n]
> Selected by [y]:
> - RISCV [=y]
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
prev parent reply other threads:[~2022-10-01 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 15:48 kernel test robot
2022-10-01 16:04 ` Conor.Dooley [this message]
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=3a05c91e-c606-c90b-5d63-29a1df6105c9@microchip.com \
--to=conor.dooley@microchip.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=liushixin2@huawei.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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