From: kernel test robot <lkp@intel.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: kbuild-all@lists.01.org, Daniel Borkmann <daniel@iogearbox.net>,
linux-kernel@vger.kernel.org
Subject: [cilium:pr/bpf-tc-links 1/10] dev.c:undefined reference to `dev_sch_uninstall'
Date: Thu, 15 Sep 2022 05:12:58 +0800 [thread overview]
Message-ID: <202209150500.kkNzJ85t-lkp@intel.com> (raw)
tree: https://github.com/cilium/linux.git pr/bpf-tc-links
head: f9ab02443a6bd720c616b575437a851435c80c49
commit: f182834c964343d39688f653f16bfee1f3ff39c2 [1/10] bpf: Add initial fd-based API to attach tc BPF programs
config: x86_64-randconfig-a002 (https://download.01.org/0day-ci/archive/20220915/202209150500.kkNzJ85t-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/cilium/linux/commit/f182834c964343d39688f653f16bfee1f3ff39c2
git remote add cilium https://github.com/cilium/linux.git
git fetch --no-tags cilium pr/bpf-tc-links
git checkout f182834c964343d39688f653f16bfee1f3ff39c2
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 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: warning: arch/x86/lib/retpoline.o: missing .note.GNU-stack section implies executable stack
ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
ld: warning: .tmp_vmlinux.kallsyms1 has a LOAD segment with RWX permissions
ld: net/core/dev.o: in function `unregister_netdevice_many':
>> dev.c:(.text+0x9368): undefined reference to `dev_sch_uninstall'
ld: net/sched/sch_ingress.o: in function `ingress_destroy':
>> sch_ingress.c:(.text+0x166): undefined reference to `sch_prog_detach_kern'
ld: net/sched/sch_ingress.o: in function `clsact_destroy':
sch_ingress.c:(.text+0x1b7): undefined reference to `sch_prog_detach_kern'
>> ld: sch_ingress.c:(.text+0x1c1): undefined reference to `sch_prog_detach_kern'
ld: net/sched/sch_ingress.o: in function `clsact_init':
>> sch_ingress.c:(.text+0x4ba): undefined reference to `sch_prog_attach_kern'
>> ld: sch_ingress.c:(.text+0x55d): undefined reference to `sch_prog_attach_kern'
ld: net/sched/sch_ingress.o: in function `ingress_init':
sch_ingress.c:(.text+0x629): undefined reference to `sch_prog_attach_kern'
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-14 21:13 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=202209150500.kkNzJ85t-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®