BPF List
 help / color / mirror / Atom feed
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 14:04:06 +0800	[thread overview]
Message-ID: <202007141359.35b5pKLH%lkp@intel.com> (raw)
In-Reply-To: <20200713182520.97606-5-zeil@yandex-team.ru>

[-- Attachment #1: Type: text/plain, Size: 2372 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: microblaze-randconfig-s031-20200714 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.2-41-g14e84ffc-dirty
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=microblaze 

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:46: sparse: sparse: using member 'effective' in incomplete struct cgroup_bpf
   net/bpf/test_run.c:53:54: sparse: sparse: using member 'effective' in incomplete struct cgroup_bpf
   net/bpf/test_run.c:67:15: sparse: sparse: undefined identifier 'bpf_cgroup_storages_alloc'
   net/bpf/test_run.c:115:9: sparse: sparse: undefined identifier 'bpf_cgroup_storages_free'

vim +25 net/bpf/test_run.c

    17	
    18	static struct bpf_prog_array_item *bpf_prog_find_active(struct bpf_prog *prog,
    19								struct bpf_prog_array *effective)
    20	{
    21		struct bpf_prog_array_item *item;
    22		struct bpf_prog_array *array;
    23		struct bpf_prog *p;
    24	
  > 25		array = rcu_dereference(effective);
    26		if (!array)
    27			return NULL;
    28	
    29		item = &array->items[0];
    30		while ((p = READ_ONCE(item->prog))) {
    31			if (p == prog)
    32				return item;
    33			item++;
    34		}
    35	
    36		return NULL;
    37	}
    38	

---
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: 24972 bytes --]

  parent reply	other threads:[~2020-07-14  6:04 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 [this message]
2020-07-14  7:09   ` kernel test robot

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=202007141359.35b5pKLH%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