From: kernel test robot <lkp@intel.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: [linux-next:master 1880/4499] ld.lld: error: undefined symbol: arm64_bpf_fixup_exception
Date: Mon, 24 May 2021 09:25:29 +0800 [thread overview]
Message-ID: <202105240924.0g1MHKBO-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2491 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8dca2cd055ffb78b37f52f0bf0bd20c249619c4d
commit: b24abcff918a5cbf44b0c982bd3477a93e8e4911 [1880/4499] bpf, kconfig: Add consolidated menu entry for bpf with core options
config: arm64-randconfig-r026-20210524 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project b4fd512c36ca344a3ff69350219e8b0a67e9472a)
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 arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b24abcff918a5cbf44b0c982bd3477a93e8e4911
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 b24abcff918a5cbf44b0c982bd3477a93e8e4911
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD 8dca2cd055ffb78b37f52f0bf0bd20c249619c4d builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: arm64_bpf_fixup_exception
>>> referenced by extable.c
>>> mm/extable.o:(fixup_exception) in archive arch/arm64/built-in.a
--
>> ld.lld: error: undefined symbol: search_bpf_extables
>>> referenced by extable.c
>>> extable.o:(search_exception_tables) in archive kernel/built-in.a
--
>> ld.lld: error: undefined symbol: is_bpf_text_address
>>> referenced by extable.c
>>> extable.o:(kernel_text_address) in archive kernel/built-in.a
--
>> ld.lld: error: undefined symbol: __bpf_address_lookup
>>> referenced by kallsyms.c
>>> kallsyms.o:(kallsyms_lookup_size_offset) in archive kernel/built-in.a
>>> referenced by kallsyms.c
>>> kallsyms.o:(kallsyms_lookup) in archive kernel/built-in.a
--
>> ld.lld: error: undefined symbol: bpf_get_kallsym
>>> referenced by kallsyms.c
>>> kallsyms.o:(kdb_walk_kallsyms) in archive kernel/built-in.a
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30769 bytes --]
next reply other threads:[~2021-05-24 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 1:25 kernel test robot [this message]
2021-05-24 11:56 ` Daniel Borkmann
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=202105240924.0g1MHKBO-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
/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