From: kernel test robot <lkp@intel.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Daniel Borkmann <daniel@iogearbox.net>,
linux-kernel@vger.kernel.org
Subject: [cilium:pr/meta4 2/2] ld.lld: error: undefined symbol: sch_prog_attach_kern
Date: Sat, 18 Jun 2022 06:13:38 +0800 [thread overview]
Message-ID: <202206180627.1kpqC1Jb-lkp@intel.com> (raw)
tree: https://github.com/cilium/linux.git pr/meta4
head: dcea837b60f0d9f8f3cdae284680659042f560d1
commit: dcea837b60f0d9f8f3cdae284680659042f560d1 [2/2] bpf: Add fd-based API to attach tc BPF programs
config: arm-randconfig-r023-20220617 (https://download.01.org/0day-ci/archive/20220618/202206180627.1kpqC1Jb-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project d764aa7fc6b9cc3fbe960019018f5f9e941eb0a6)
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 arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://github.com/cilium/linux/commit/dcea837b60f0d9f8f3cdae284680659042f560d1
git remote add cilium https://github.com/cilium/linux.git
git fetch --no-tags cilium pr/meta4
git checkout dcea837b60f0d9f8f3cdae284680659042f560d1
# 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=arm 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 >>):
>> ld.lld: error: undefined symbol: sch_prog_attach_kern
>>> referenced by sch_ingress.c
>>> sched/sch_ingress.o:(ingress_init) in archive net/built-in.a
>>> referenced by sch_ingress.c
>>> sched/sch_ingress.o:(clsact_init) in archive net/built-in.a
>>> referenced by sch_ingress.c
>>> sched/sch_ingress.o:(clsact_init) in archive net/built-in.a
--
>> ld.lld: error: undefined symbol: sch_prog_detach_kern
>>> referenced by sch_ingress.c
>>> sched/sch_ingress.o:(ingress_destroy) in archive net/built-in.a
>>> referenced by sch_ingress.c
>>> sched/sch_ingress.o:(clsact_destroy) in archive net/built-in.a
>>> referenced by sch_ingress.c
>>> sched/sch_ingress.o:(clsact_destroy) in archive net/built-in.a
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-17 22:14 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=202206180627.1kpqC1Jb-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®