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-next20240305 1/1] include/linux/bpf-cgroup.h:191:22: sparse: sparse: incompatible types in comparison expression (different base types):
Date: Sat, 9 Mar 2024 02:44:19 +0800 [thread overview]
Message-ID: <202403090203.mM0o7gTP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git testing/WFAMNAE-next20240305
head: 3a02035a7f980ddbf41dd11815bb4e5f29e104d5
commit: 3a02035a7f980ddbf41dd11815bb4e5f29e104d5 [1/1] treewide: Address -Wflex-array-member-not-at-end warnings
config: x86_64-randconfig-122-20240308 (https://download.01.org/0day-ci/archive/20240309/202403090203.mM0o7gTP-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240309/202403090203.mM0o7gTP-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/202403090203.mM0o7gTP-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
net/socket.c: note: in included file:
>> include/linux/bpf-cgroup.h:191:22: sparse: sparse: incompatible types in comparison expression (different base types):
include/linux/bpf-cgroup.h:191:22: sparse: struct bpf_prog_array *
include/linux/bpf-cgroup.h:191:22: sparse: struct bpf_prog_array_hdr *
>> include/linux/bpf-cgroup.h:191:22: sparse: sparse: incompatible types in comparison expression (different base types):
include/linux/bpf-cgroup.h:191:22: sparse: struct bpf_prog_array *
include/linux/bpf-cgroup.h:191:22: sparse: struct bpf_prog_array_hdr *
vim +191 include/linux/bpf-cgroup.h
de9cbbaadba5ad Roman Gushchin 2018-08-02 178
b741f1630346de Roman Gushchin 2018-09-28 179 int bpf_percpu_cgroup_storage_copy(struct bpf_map *map, void *key, void *value);
b741f1630346de Roman Gushchin 2018-09-28 180 int bpf_percpu_cgroup_storage_update(struct bpf_map *map, void *key,
b741f1630346de Roman Gushchin 2018-09-28 181 void *value, u64 flags);
b741f1630346de Roman Gushchin 2018-09-28 182
46531a30364bd4 Pavel Begunkov 2022-01-27 183 /* Opportunistic check to see whether we have any BPF program attached*/
46531a30364bd4 Pavel Begunkov 2022-01-27 184 static inline bool cgroup_bpf_sock_enabled(struct sock *sk,
46531a30364bd4 Pavel Begunkov 2022-01-27 185 enum cgroup_bpf_attach_type type)
46531a30364bd4 Pavel Begunkov 2022-01-27 186 {
46531a30364bd4 Pavel Begunkov 2022-01-27 187 struct cgroup *cgrp = sock_cgroup_ptr(&sk->sk_cgrp_data);
46531a30364bd4 Pavel Begunkov 2022-01-27 188 struct bpf_prog_array *array;
46531a30364bd4 Pavel Begunkov 2022-01-27 189
46531a30364bd4 Pavel Begunkov 2022-01-27 190 array = rcu_access_pointer(cgrp->bpf.effective[type]);
46531a30364bd4 Pavel Begunkov 2022-01-27 @191 return array != &bpf_empty_prog_array.hdr;
46531a30364bd4 Pavel Begunkov 2022-01-27 192 }
46531a30364bd4 Pavel Begunkov 2022-01-27 193
:::::: The code at line 191 was first introduced by commit
:::::: 46531a30364bd483bfa1b041c15d42a196e77e93 cgroup/bpf: fast path skb BPF filtering
:::::: TO: Pavel Begunkov <asml.silence@gmail.com>
:::::: CC: Alexei Starovoitov <ast@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-08 18:45 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=202403090203.mM0o7gTP-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.