From: kernel test robot <lkp@intel.com>
To: thinker.li@gmail.com, bpf@vger.kernel.org, ast@kernel.org,
martin.lau@linux.dev, song@kernel.org, kernel-team@meta.com,
andrii@kernel.org, drosen@google.com
Cc: oe-kbuild-all@lists.linux.dev, sinquersw@gmail.com,
kuifeng@meta.com, Kui-Feng Lee <thinker.li@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v10 10/13] bpf, net: switch to dynamic registration
Date: Sun, 5 Nov 2023 13:16:09 +0800 [thread overview]
Message-ID: <202311051202.DeubcWTl-lkp@intel.com> (raw)
In-Reply-To: <20231103232202.3664407-11-thinker.li@gmail.com>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/thinker-li-gmail-com/bpf-refactory-struct_ops-type-initialization-to-a-function/20231104-072528
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20231103232202.3664407-11-thinker.li%40gmail.com
patch subject: [PATCH bpf-next v10 10/13] bpf, net: switch to dynamic registration
config: riscv-randconfig-002-20231105 (https://download.01.org/0day-ci/archive/20231105/202311051202.DeubcWTl-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231105/202311051202.DeubcWTl-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/202311051202.DeubcWTl-lkp@intel.com/
All errors (new ones prefixed by >>):
riscv64-linux-ld: kernel/bpf/btf.o: in function `btf_array_show':
>> kernel/bpf/btf.c:3044:(.text+0x6c38): undefined reference to `bpf_struct_ops_desc_init'
vim +3044 kernel/bpf/btf.c
31d0bc81637d8d Alan Maguire 2020-09-28 3032
31d0bc81637d8d Alan Maguire 2020-09-28 3033 static void btf_array_show(const struct btf *btf, const struct btf_type *t,
31d0bc81637d8d Alan Maguire 2020-09-28 3034 u32 type_id, void *data, u8 bits_offset,
31d0bc81637d8d Alan Maguire 2020-09-28 3035 struct btf_show *show)
31d0bc81637d8d Alan Maguire 2020-09-28 3036 {
31d0bc81637d8d Alan Maguire 2020-09-28 3037 const struct btf_member *m = show->state.member;
31d0bc81637d8d Alan Maguire 2020-09-28 3038
31d0bc81637d8d Alan Maguire 2020-09-28 3039 /*
31d0bc81637d8d Alan Maguire 2020-09-28 3040 * First check if any members would be shown (are non-zero).
31d0bc81637d8d Alan Maguire 2020-09-28 3041 * See comments above "struct btf_show" definition for more
31d0bc81637d8d Alan Maguire 2020-09-28 3042 * details on how this works at a high-level.
31d0bc81637d8d Alan Maguire 2020-09-28 3043 */
31d0bc81637d8d Alan Maguire 2020-09-28 @3044 if (show->state.depth > 0 && !(show->flags & BTF_SHOW_ZERO)) {
31d0bc81637d8d Alan Maguire 2020-09-28 3045 if (!show->state.depth_check) {
31d0bc81637d8d Alan Maguire 2020-09-28 3046 show->state.depth_check = show->state.depth + 1;
31d0bc81637d8d Alan Maguire 2020-09-28 3047 show->state.depth_to_show = 0;
31d0bc81637d8d Alan Maguire 2020-09-28 3048 }
31d0bc81637d8d Alan Maguire 2020-09-28 3049 __btf_array_show(btf, t, type_id, data, bits_offset, show);
31d0bc81637d8d Alan Maguire 2020-09-28 3050 show->state.member = m;
31d0bc81637d8d Alan Maguire 2020-09-28 3051
31d0bc81637d8d Alan Maguire 2020-09-28 3052 if (show->state.depth_check != show->state.depth + 1)
31d0bc81637d8d Alan Maguire 2020-09-28 3053 return;
31d0bc81637d8d Alan Maguire 2020-09-28 3054 show->state.depth_check = 0;
31d0bc81637d8d Alan Maguire 2020-09-28 3055
31d0bc81637d8d Alan Maguire 2020-09-28 3056 if (show->state.depth_to_show <= show->state.depth)
31d0bc81637d8d Alan Maguire 2020-09-28 3057 return;
31d0bc81637d8d Alan Maguire 2020-09-28 3058 /*
31d0bc81637d8d Alan Maguire 2020-09-28 3059 * Reaching here indicates we have recursed and found
31d0bc81637d8d Alan Maguire 2020-09-28 3060 * non-zero array member(s).
31d0bc81637d8d Alan Maguire 2020-09-28 3061 */
31d0bc81637d8d Alan Maguire 2020-09-28 3062 }
31d0bc81637d8d Alan Maguire 2020-09-28 3063 __btf_array_show(btf, t, type_id, data, bits_offset, show);
b00b8daec828dd Martin KaFai Lau 2018-04-18 3064 }
b00b8daec828dd Martin KaFai Lau 2018-04-18 3065
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-05 5:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 23:21 [PATCH bpf-next v10 00/13] Registrating struct_ops types from modules thinker.li
2023-11-03 23:21 ` [PATCH bpf-next v10 01/13] bpf: refactory struct_ops type initialization to a function thinker.li
2023-11-03 23:21 ` [PATCH bpf-next v10 02/13] bpf: get type information with BPF_ID_LIST thinker.li
2023-11-03 23:21 ` [PATCH bpf-next v10 03/13] bpf, net: introduce bpf_struct_ops_desc thinker.li
2023-11-03 23:21 ` [PATCH bpf-next v10 04/13] bpf: add struct_ops_tab to btf thinker.li
2023-11-03 23:21 ` [PATCH bpf-next v10 05/13] bpf: make struct_ops_map support btfs other than btf_vmlinux thinker.li
2023-11-03 23:21 ` [PATCH bpf-next v10 06/13] bpf: lookup struct_ops types from a given module BTF thinker.li
2023-11-03 23:21 ` [PATCH bpf-next v10 07/13] bpf: pass attached BTF to the bpf_struct_ops subsystem thinker.li
2023-11-03 23:21 ` [PATCH bpf-next v10 08/13] bpf: hold module for bpf_struct_ops_map thinker.li
2023-11-03 23:21 ` [PATCH bpf-next v10 09/13] bpf: validate value_type thinker.li
2023-11-03 23:21 ` [PATCH bpf-next v10 10/13] bpf, net: switch to dynamic registration thinker.li
2023-11-05 5:16 ` kernel test robot [this message]
2023-11-03 23:22 ` [PATCH bpf-next v10 11/13] libbpf: Find correct module BTFs for struct_ops maps and progs thinker.li
2023-11-03 23:22 ` [PATCH bpf-next v10 12/13] bpf: export btf_ctx_access to modules thinker.li
2023-11-03 23:22 ` [PATCH bpf-next v10 13/13] selftests/bpf: test case for register_bpf_struct_ops() thinker.li
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=202311051202.DeubcWTl-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=drosen@google.com \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sinquersw@gmail.com \
--cc=song@kernel.org \
--cc=thinker.li@gmail.com \
/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.