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-next20250124 15/15] kernel/bpf/core.c:2510:29: sparse: sparse: incompatible types in comparison expression (different base types):
Date: Tue, 28 Jan 2025 14:10:52 +0800 [thread overview]
Message-ID: <202501281414.ABnepGOJ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git testing/wfamnae-next20250124
head: 86b653e4edef7b0f7b7afe5dd8e0241fc1165238
commit: 9fcf89847632bd963953b2f945fb3ce2277f1f97 [15/15] treewide_some: fix multiple -Wfamnae warnings that must be audited separately
config: i386-randconfig-062-20250128 (https://download.01.org/0day-ci/archive/20250128/202501281414.ABnepGOJ-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250128/202501281414.ABnepGOJ-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/202501281414.ABnepGOJ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
kernel/bpf/core.c:243:49: sparse: sparse: arithmetics on pointers to functions
kernel/bpf/core.c:2015:43: sparse: sparse: arithmetics on pointers to functions
kernel/bpf/core.c:2020:48: sparse: sparse: arithmetics on pointers to functions
kernel/bpf/core.c:2288:77: sparse: sparse: subtraction of functions? Share your drugs
>> kernel/bpf/core.c:2510:29: sparse: sparse: incompatible types in comparison expression (different base types):
kernel/bpf/core.c:2510:29: sparse: struct bpf_prog_array *
kernel/bpf/core.c:2510: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:321:1: sparse: sparse: Using plain integer as NULL pointer
include/trace/events/xdp.h:348:1: sparse: sparse: Using plain integer as NULL pointer
include/trace/events/xdp.h:382: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:74:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/rbtree.h:74:9: sparse: struct rb_node [noderef] __rcu *
include/linux/rbtree.h:74:9: sparse: struct rb_node *
include/linux/rbtree.h:74:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/rbtree.h:74:9: sparse: struct rb_node [noderef] __rcu *
include/linux/rbtree.h:74:9: sparse: struct rb_node *
vim +2510 kernel/bpf/core.c
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2507
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2508 void bpf_prog_array_free_sleepable(struct bpf_prog_array *progs)
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2509 {
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 @2510 if (!progs || progs == &bpf_empty_prog_array.hdr)
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2511 return;
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2512 call_rcu_tasks_trace(&progs->rcu, __bpf_prog_array_free_sleepable_cb);
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2513 }
8c7dcb84e3b744 Delyan Kratunov 2022-06-14 2514
:::::: The code at line 2510 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-01-28 6:11 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=202501281414.ABnepGOJ-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox