From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [congwang:sockmap3 1/10] syscall.c:undefined reference to `bpf_fd_reuseport_array_update_elem'
Date: Thu, 22 Apr 2021 08:42:53 +0800 [thread overview]
Message-ID: <202104220850.yBxJaJuI-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
tree: https://github.com/congwang/linux.git sockmap3
head: e5d5ad90185716657e7f42a34f50a192c9a1f265
commit: d7a8a50ed800a43ecd8eed96293aa5015f9fd7be [1/10] sock_map: extend support beyond INET
config: riscv-randconfig-r034-20210421 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.0
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
# https://github.com/congwang/linux/commit/d7a8a50ed800a43ecd8eed96293aa5015f9fd7be
git remote add congwang https://github.com/congwang/linux.git
git fetch --no-tags congwang sockmap3
git checkout d7a8a50ed800a43ecd8eed96293aa5015f9fd7be
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=riscv
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 >>):
riscv64-linux-ld: kernel/bpf/syscall.o: in function `.L222':
>> syscall.c:(.text+0xb8a): undefined reference to `bpf_fd_reuseport_array_update_elem'
riscv64-linux-ld: kernel/bpf/syscall.o: in function `bpf_map_do_batch':
>> syscall.c:(.text+0x2192): undefined reference to `bpf_fd_reuseport_array_lookup_elem'
riscv64-linux-ld: net/core/sock_reuseport.o: in function `.L0 ':
>> sock_reuseport.c:(.text+0x444): undefined reference to `bpf_sk_reuseport_detach'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 26548 bytes --]
reply other threads:[~2021-04-22 0:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202104220850.yBxJaJuI-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.