From: kernel test robot <lkp@intel.com>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>
Subject: [bpf-next:for-next 1055/1059] kernel/bpf/task_iter.c:593: undefined reference to `btf_task_struct_ids'
Date: Thu, 26 Aug 2021 03:49:24 +0800 [thread overview]
Message-ID: <202108260318.CCV4KpWu-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2075 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git for-next
head: 35cba2988fc65239d10566edc03cc0978382c25f
commit: 33c5cb36015ac1034b50b823fae367e908d05147 [1055/1059] bpf: Consolidate task_struct BTF_ID declarations
config: x86_64-randconfig-p001-20210825 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=33c5cb36015ac1034b50b823fae367e908d05147
git remote add bpf-next https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
git fetch --no-tags bpf-next for-next
git checkout 33c5cb36015ac1034b50b823fae367e908d05147
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 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: kernel/bpf/task_iter.o: in function `task_iter_init':
>> kernel/bpf/task_iter.c:593: undefined reference to `btf_task_struct_ids'
>> ld: kernel/bpf/task_iter.c:598: undefined reference to `btf_task_struct_ids'
ld: kernel/bpf/task_iter.c:604: undefined reference to `btf_task_struct_ids'
>> ld: kernel/bpf/bpf_task_storage.o:(.rodata+0x110): undefined reference to `btf_task_struct_ids'
ld: kernel/bpf/bpf_task_storage.o:(.rodata+0x170): undefined reference to `btf_task_struct_ids'
ld: kernel/bpf/stackmap.o:(.rodata+0x328): more undefined references to `btf_task_struct_ids' follow
vim +593 kernel/bpf/task_iter.c
588
589 static int __init task_iter_init(void)
590 {
591 int ret;
592
> 593 task_reg_info.ctx_arg_info[0].btf_id = btf_task_struct_ids[0];
594 ret = bpf_iter_reg_target(&task_reg_info);
595 if (ret)
596 return ret;
597
> 598 task_file_reg_info.ctx_arg_info[0].btf_id = btf_task_struct_ids[0];
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35045 bytes --]
reply other threads:[~2021-08-25 19:50 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=202108260318.CCV4KpWu-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=dxu@dxuuu.xyz \
--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®