From: kernel test robot <lkp@intel.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [gustavoars:testing/wfamnae-next20251212 21/21] kernel/bpf/core.c:2624:29: sparse: sparse: incompatible types in comparison expression (different base types):
Date: Sat, 13 Dec 2025 21:47:38 +0800 [thread overview]
Message-ID: <202512132156.6jTMbPEC-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git testing/wfamnae-next20251212
head: c3cc47915438797b3342f426772472b7c3dee6df
commit: c3cc47915438797b3342f426772472b7c3dee6df [21/21] treewide_some: fix multiple -Wfamnae warnings that must be audited separately
config: s390-randconfig-r112-20251213 (https://download.01.org/0day-ci/archive/20251213/202512132156.6jTMbPEC-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 1335a05ab8bc8339ce24be3a9da89d8c3f4e0571)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251213/202512132156.6jTMbPEC-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/202512132156.6jTMbPEC-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
kernel/bpf/core.c:250:49: sparse: sparse: arithmetics on pointers to functions
kernel/bpf/core.c:2037:43: sparse: sparse: arithmetics on pointers to functions
kernel/bpf/core.c:2042:48: sparse: sparse: arithmetics on pointers to functions
kernel/bpf/core.c:2363:77: sparse: sparse: subtraction of functions? Share your drugs
>> kernel/bpf/core.c:2624:29: sparse: sparse: incompatible types in comparison expression (different base types):
kernel/bpf/core.c:2624:29: sparse: struct bpf_prog_array *
kernel/bpf/core.c:2624:29: sparse: struct bpf_prog_array_hdr *
kernel/bpf/core.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/xdp.h, ...):
include/trace/events/xdp.h:304:1: sparse: sparse: Using plain integer as NULL pointer
include/trace/events/xdp.h:331:1: sparse: sparse: Using plain integer as NULL pointer
kernel/bpf/core.c: note: in included file (through include/linux/rbtree_latch.h, include/linux/bpf.h, include/linux/filter.h):
include/linux/rbtree.h:102:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/rbtree.h:102:9: sparse: struct rb_node [noderef] __rcu *
include/linux/rbtree.h:102:9: sparse: struct rb_node *
include/linux/rbtree.h:102:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/rbtree.h:102:9: sparse: struct rb_node [noderef] __rcu *
include/linux/rbtree.h:102:9: sparse: struct rb_node *
vim +2624 kernel/bpf/core.c
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2621
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2622 void bpf_prog_array_free_sleepable(struct bpf_prog_array *progs)
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2623 {
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 @2624 if (!progs || progs == &bpf_empty_prog_array.hdr)
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2625 return;
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2626 call_rcu_tasks_trace(&progs->rcu, __bpf_prog_array_free_sleepable_cb);
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2627 }
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2628
:::::: The code at line 2624 was first introduced by commit
:::::: 8c7dcb84e3b744b2b70baa7a44a9b1881c33a9c9 bpf: implement sleepable uprobes by chaining gps
:::::: TO: Delyan Kratunov <delyank@fb.com>
:::::: CC: Alexei Starovoitov <ast@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-13 13:47 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=202512132156.6jTMbPEC-lkp@intel.com \
--to=lkp@intel.com \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--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.