From: kernel test robot <lkp@intel.com>
To: Aditi Ghag <aditi.ghag@isovalent.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Martin KaFai Lau <martin.lau@kernel.org>
Subject: WARN: resolve_btfids: unresolved symbol bpf_sock_destroy
Date: Mon, 25 Dec 2023 17:51:48 +0800 [thread overview]
Message-ID: <202312251746.AJnSCuzj-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 861deac3b092f37b2c5e6871732f3e11486f7082
commit: 4ddbcb886268af8d12a23e6640b39d1d9c652b1b bpf: Add bpf_sock_destroy kfunc
date: 7 months ago
config: mips-randconfig-r001-20230703 (https://download.01.org/0day-ci/archive/20231225/202312251746.AJnSCuzj-lkp@intel.com/config)
compiler: mips64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231225/202312251746.AJnSCuzj-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/202312251746.AJnSCuzj-lkp@intel.com/
All warnings (new ones prefixed by >>):
WARN: resolve_btfids: unresolved symbol unix_sock
WARN: resolve_btfids: unresolved symbol bpf_cpumask
WARN: resolve_btfids: unresolved symbol bpf_xdp_metadata_rx_timestamp
WARN: resolve_btfids: unresolved symbol bpf_xdp_metadata_rx_hash
WARN: resolve_btfids: unresolved symbol bpf_xdp_ct_lookup
WARN: resolve_btfids: unresolved symbol bpf_xdp_ct_alloc
WARN: resolve_btfids: unresolved symbol bpf_task_under_cgroup
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_sock_destroy
WARN: resolve_btfids: unresolved symbol bpf_skb_set_fou_encap
WARN: resolve_btfids: unresolved symbol bpf_skb_get_fou_encap
WARN: resolve_btfids: unresolved symbol bpf_skb_ct_lookup
WARN: resolve_btfids: unresolved symbol bpf_skb_ct_alloc
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_modify_return_test
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_kfunc_call_test_release
WARN: resolve_btfids: unresolved symbol bpf_kfunc_call_memb_release
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_size
WARN: resolve_btfids: unresolved symbol bpf_dynptr_is_rdonly
WARN: resolve_btfids: unresolved symbol bpf_dynptr_is_null
WARN: resolve_btfids: unresolved symbol bpf_dynptr_from_xdp
WARN: resolve_btfids: unresolved symbol bpf_dynptr_clone
WARN: resolve_btfids: unresolved symbol bpf_dynptr_adjust
WARN: resolve_btfids: unresolved symbol bpf_ct_set_timeout
WARN: resolve_btfids: unresolved symbol bpf_ct_set_status
WARN: resolve_btfids: unresolved symbol bpf_ct_set_nat_info
WARN: resolve_btfids: unresolved symbol bpf_ct_release
WARN: resolve_btfids: unresolved symbol bpf_ct_insert_entry
WARN: resolve_btfids: unresolved symbol bpf_ct_change_timeout
WARN: resolve_btfids: unresolved symbol bpf_ct_change_status
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-25 9:52 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=202312251746.AJnSCuzj-lkp@intel.com \
--to=lkp@intel.com \
--cc=aditi.ghag@isovalent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@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 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®