From: kernel test robot <lkp@intel.com>
To: Dmitry Yakunin <zeil@yandex-team.ru>,
alexei.starovoitov@gmail.com, daniel@iogearbox.net,
netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: kbuild-all@lists.01.org, sdf@google.com
Subject: Re: [PATCH bpf-next 4/4] bpf: try to use existing cgroup storage in bpf_prog_test_run_skb
Date: Tue, 14 Jul 2020 15:09:01 +0800 [thread overview]
Message-ID: <202007141548.s7cinYSs%lkp@intel.com> (raw)
In-Reply-To: <20200713182520.97606-5-zeil@yandex-team.ru>
[-- Attachment #1: Type: text/plain, Size: 2641 bytes --]
Hi Dmitry,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Dmitry-Yakunin/bpf-cgroup-skb-improvements-for-bpf_prog_test_run/20200714-022728
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: x86_64-randconfig-s022-20200714 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-41-g14e84ffc-dirty
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
net/bpf/test_run.c:25:17: sparse: sparse: incompatible types in comparison expression (different address spaces):
net/bpf/test_run.c:25:17: sparse: struct bpf_prog_array [noderef] __rcu *
net/bpf/test_run.c:25:17: sparse: struct bpf_prog_array *
>> net/bpf/test_run.c:50:56: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct bpf_prog_array *[addressable] effective @@ got struct bpf_prog_array [noderef] __rcu * @@
>> net/bpf/test_run.c:50:56: sparse: expected struct bpf_prog_array *[addressable] effective
>> net/bpf/test_run.c:50:56: sparse: got struct bpf_prog_array [noderef] __rcu *
net/bpf/test_run.c:53:64: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct bpf_prog_array *[addressable] effective @@ got struct bpf_prog_array [noderef] __rcu * @@
net/bpf/test_run.c:53:64: sparse: expected struct bpf_prog_array *[addressable] effective
net/bpf/test_run.c:53:64: sparse: got struct bpf_prog_array [noderef] __rcu *
vim +50 net/bpf/test_run.c
38
39 static struct bpf_cgroup_storage **bpf_prog_find_active_storage(struct bpf_prog *prog)
40 {
41 struct bpf_prog_array_item *item;
42 struct cgroup *cgrp;
43
44 if (prog->type != BPF_PROG_TYPE_CGROUP_SKB)
45 return NULL;
46
47 cgrp = task_dfl_cgroup(current);
48
49 item = bpf_prog_find_active(prog,
> 50 cgrp->bpf.effective[BPF_CGROUP_INET_INGRESS]);
51 if (!item)
52 item = bpf_prog_find_active(prog,
53 cgrp->bpf.effective[BPF_CGROUP_INET_EGRESS]);
54
55 return item ? item->cgroup_storage : NULL;
56 }
57
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31714 bytes --]
prev parent reply other threads:[~2020-07-14 7:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 18:25 [PATCH bpf-next 0/4] bpf: cgroup skb improvements for bpf_prog_test_run Dmitry Yakunin
2020-07-13 18:25 ` [PATCH bpf-next 1/4] bpf: setup socket family and addresses in bpf_prog_test_run_skb Dmitry Yakunin
2020-07-13 18:25 ` [PATCH bpf-next 2/4] bpf: allow to specify ifindex for skb " Dmitry Yakunin
2020-07-13 18:25 ` [PATCH bpf-next 3/4] bpf: export some cgroup storages allocation helpers for reusing Dmitry Yakunin
2020-07-13 22:17 ` kernel test robot
2020-07-14 3:25 ` kernel test robot
2020-07-13 18:25 ` [PATCH bpf-next 4/4] bpf: try to use existing cgroup storage in bpf_prog_test_run_skb Dmitry Yakunin
2020-07-13 22:36 ` kernel test robot
2020-07-14 1:14 ` kernel test robot
2020-07-14 6:04 ` kernel test robot
2020-07-14 7:09 ` kernel test robot [this message]
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=202007141548.s7cinYSs%lkp@intel.com \
--to=lkp@intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=zeil@yandex-team.ru \
/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;
as well as URLs for NNTP newsgroup(s).