From: kernel test robot <lkp@intel.com>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Subject: WARN: resolve_btfids: unresolved symbol bpf_dynptr_adjust
Date: Sun, 24 Dec 2023 20:18:16 +0800 [thread overview]
Message-ID: <202312242048.UIDTfHDC-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 861deac3b092f37b2c5e6871732f3e11486f7082
commit: 987d0242d189661f78b77cc4d77f843b15600fed bpf: Add bpf_dynptr_adjust
date: 8 months ago
config: powerpc-randconfig-r002-20220613 (https://download.01.org/0day-ci/archive/20231224/202312242048.UIDTfHDC-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231224/202312242048.UIDTfHDC-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/202312242048.UIDTfHDC-lkp@intel.com/
All warnings (new ones prefixed by >>):
WARN: resolve_btfids: unresolved symbol prog_test_ref_kfunc
WARN: resolve_btfids: unresolved symbol bpf_cpumask
WARN: resolve_btfids: unresolved symbol bpf_task_release
WARN: resolve_btfids: unresolved symbol bpf_task_from_pid
WARN: resolve_btfids: unresolved symbol bpf_task_acquire
WARN: resolve_btfids: unresolved symbol bpf_refcount_acquire_impl
WARN: resolve_btfids: unresolved symbol bpf_rdonly_cast
WARN: resolve_btfids: unresolved symbol bpf_rcu_read_unlock
WARN: resolve_btfids: unresolved symbol bpf_rcu_read_lock
WARN: resolve_btfids: unresolved symbol bpf_rbtree_remove
WARN: resolve_btfids: unresolved symbol bpf_rbtree_first
WARN: resolve_btfids: unresolved symbol bpf_rbtree_add_impl
WARN: resolve_btfids: unresolved symbol bpf_obj_new_impl
WARN: resolve_btfids: unresolved symbol bpf_obj_drop_impl
WARN: resolve_btfids: unresolved symbol bpf_list_push_front_impl
WARN: resolve_btfids: unresolved symbol bpf_list_push_back_impl
WARN: resolve_btfids: unresolved symbol bpf_list_pop_front
WARN: resolve_btfids: unresolved symbol bpf_list_pop_back
WARN: resolve_btfids: unresolved symbol bpf_iter_num_next
WARN: resolve_btfids: unresolved symbol bpf_iter_num_new
WARN: resolve_btfids: unresolved symbol bpf_iter_num_destroy
WARN: resolve_btfids: unresolved symbol bpf_dynptr_slice_rdwr
WARN: resolve_btfids: unresolved symbol bpf_dynptr_slice
WARN: resolve_btfids: unresolved symbol bpf_dynptr_from_xdp
WARN: resolve_btfids: unresolved symbol bpf_dynptr_from_skb
>> WARN: resolve_btfids: unresolved symbol bpf_dynptr_adjust
WARN: resolve_btfids: unresolved symbol bpf_cgroup_release
WARN: resolve_btfids: unresolved symbol bpf_cgroup_from_id
WARN: resolve_btfids: unresolved symbol bpf_cgroup_ancestor
WARN: resolve_btfids: unresolved symbol bpf_cgroup_acquire
WARN: resolve_btfids: unresolved symbol bpf_cast_to_kern_ctx
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-24 12:20 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=202312242048.UIDTfHDC-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=daniel@iogearbox.net \
--cc=joannelkoong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.