From: kernel test robot <lkp@intel.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: oe-kbuild-all@lists.linux.dev, Daniel Borkmann <daniel@iogearbox.net>
Subject: [cilium:pr/misc-patches 10/13] nios2-linux-ld: task_iter.c:undefined reference to `init_net'
Date: Sun, 12 May 2024 00:18:48 +0800 [thread overview]
Message-ID: <202405120025.GaFABc22-lkp@intel.com> (raw)
tree: https://github.com/cilium/linux.git pr/misc-patches
head: 3c68876290b3daed7a2766d683c73bbb4fa5b3d1
commit: 32d03d460ba261b39cb694e6140d84f2f67c3f8d [10/13] bpf: kfunc for init netns
config: nios2-randconfig-001-20240511 (https://download.01.org/0day-ci/archive/20240512/202405120025.GaFABc22-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240512/202405120025.GaFABc22-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202405120025.GaFABc22-lkp@intel.com/
All errors (new ones prefixed by >>):
nios2-linux-ld: kernel/bpf/task_iter.o: in function `bpf_iter_net_new':
task_iter.c:(.text+0x16fc): undefined reference to `net_namespace_list'
nios2-linux-ld: task_iter.c:(.text+0x1700): undefined reference to `net_namespace_list'
nios2-linux-ld: task_iter.c:(.text+0x1704): undefined reference to `net_namespace_list'
nios2-linux-ld: task_iter.c:(.text+0x1708): undefined reference to `net_namespace_list'
nios2-linux-ld: kernel/bpf/task_iter.o: in function `bpf_init_net':
task_iter.c:(.text+0x17e4): undefined reference to `init_net'
>> nios2-linux-ld: task_iter.c:(.text+0x17e8): undefined reference to `init_net'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-11 16:19 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=202405120025.GaFABc22-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel@iogearbox.net \
--cc=oe-kbuild-all@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).