From: tongtiangen <tongtiangen@huawei.com>
To: Daniel Borkmann <daniel@iogearbox.net>,
kernel test robot <lkp@intel.com>
Cc: <llvm@lists.linux.dev>, <kbuild-all@lists.01.org>,
"Linux Memory Management List" <linux-mm@kvack.org>,
<bjorn@kernel.org>, <ast@kernel.org>
Subject: Re: [linux-next:master 11539/12851] ld.lld: error: undefined symbol: rv_bpf_fixup_exception
Date: Tue, 2 Nov 2021 11:36:47 +0800 [thread overview]
Message-ID: <ad29c5af-338e-c56d-f227-8a5c0a63bc24@huawei.com> (raw)
In-Reply-To: <5e9622c3-9ee1-6693-5eea-805c5eee2047@iogearbox.net>
Hi Daniel:
I'll confirm and fix this issue later.
On 2021/11/2 6:33, Daniel Borkmann wrote:
> Tong, please fix this up ASAP; already pinged you once about it last Thursday.
>
> Thanks!
>
> On 11/1/21 11:15 PM, kernel test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head: 9febf119430617d18e1b6ee4b41ce7b07965e21f
>> commit: 252c765bd764a246a8bd516fabf6d6123df4a24f [11539/12851] riscv, bpf: Add BPF exception tables
>> config: riscv-randconfig-r036-20211101 (attached as .config)
>> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 82ed106567063ea269c6d5669278b733e173a42f)
>> 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=252c765bd764a246a8bd516fabf6d6123df4a24f
>> 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 252c765bd764a246a8bd516fabf6d6123df4a24f
>> # save the attached .config to linux build tree
>> mkdir build_dir
>> 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 as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>>> ld.lld: error: undefined symbol: rv_bpf_fixup_exception
>> >>> referenced by extable.c
>> >>> mm/extable.o:(fixup_exception) in archive arch/riscv/built-in.a
>>
>> ---
>> 0-DAY CI Kernel Test Service, Intel Corporation
>> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>>
>
> .
>
prev parent reply other threads:[~2021-11-02 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 22:15 kernel test robot
2021-11-01 22:33 ` Daniel Borkmann
2021-11-02 3:36 ` tongtiangen [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=ad29c5af-338e-c56d-f227-8a5c0a63bc24@huawei.com \
--to=tongtiangen@huawei.com \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--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