From: kernel test robot <lkp@intel.com>
To: Hangbin Liu <liuhangbin@gmail.com>, bpf@vger.kernel.org
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Jiri Benc" <jbenc@redhat.com>,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
"Eelco Chaudron" <echaudro@redhat.com>,
ast@kernel.org, "Daniel Borkmann" <daniel@iogearbox.net>,
"Lorenzo Bianconi" <lorenzo.bianconi@redhat.com>,
"David Ahern" <dsahern@gmail.com>
Subject: Re: [PATCH bpf-next 2/4] xdp: extend xdp_redirect_map with broadcast support
Date: Tue, 9 Mar 2021 16:22:44 +0800 [thread overview]
Message-ID: <202103091607.YXhmDMeL-lkp@intel.com> (raw)
In-Reply-To: <20210309072948.2127710-3-liuhangbin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4082 bytes --]
Hi Hangbin,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
url: https://github.com/0day-ci/linux/commits/Hangbin-Liu/xdp-extend-xdp_redirect_map-with-broadcast-support/20210309-153218
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: s390-randconfig-s031-20210309 (attached as .config)
compiler: s390-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.3-262-g5e674421-dirty
# https://github.com/0day-ci/linux/commit/d0e1734db001fb56c1428e92145c7f3a001402f3
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Hangbin-Liu/xdp-extend-xdp_redirect_map-with-broadcast-support/20210309-153218
git checkout d0e1734db001fb56c1428e92145c7f3a001402f3
# 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=s390
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
net/core/filter.c: In function '__bpf_tx_xdp_map':
>> net/core/filter.c:3928:15: error: 'BPF_F_REDIR_BROADCAST' undeclared (first use in this function); did you mean 'BPF_F_BROADCAST'?
3928 | if (flags & BPF_F_REDIR_BROADCAST)
| ^~~~~~~~~~~~~~~~~~~~~
| BPF_F_BROADCAST
net/core/filter.c:3928:15: note: each undeclared identifier is reported only once for each function it appears in
>> net/core/filter.c:3930:20: error: 'BPF_F_REDIR_EXCLUDE_INGRESS' undeclared (first use in this function); did you mean 'BPF_F_EXCLUDE_INGRESS'?
3930 | flags & BPF_F_REDIR_EXCLUDE_INGRESS);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
| BPF_F_EXCLUDE_INGRESS
net/core/filter.c: In function 'xdp_do_generic_redirect_map':
net/core/filter.c:4090:19: error: 'BPF_F_REDIR_BROADCAST' undeclared (first use in this function); did you mean 'BPF_F_BROADCAST'?
4090 | if (ri->flags & BPF_F_REDIR_BROADCAST)
| ^~~~~~~~~~~~~~~~~~~~~
| BPF_F_BROADCAST
net/core/filter.c:4092:24: error: 'BPF_F_REDIR_EXCLUDE_INGRESS' undeclared (first use in this function); did you mean 'BPF_F_EXCLUDE_INGRESS'?
4092 | ri->flags & BPF_F_REDIR_EXCLUDE_INGRESS);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
| BPF_F_EXCLUDE_INGRESS
net/core/filter.c: In function '____bpf_xdp_redirect_map':
net/core/filter.c:4182:44: error: 'BPF_F_REDIR_BROADCAST' undeclared (first use in this function); did you mean 'BPF_F_BROADCAST'?
4182 | if (unlikely(!ri->tgt_value) && !(flags & BPF_F_REDIR_BROADCAST)) {
| ^~~~~~~~~~~~~~~~~~~~~
| BPF_F_BROADCAST
vim +3928 net/core/filter.c
3920
3921 static int __bpf_tx_xdp_map(struct net_device *dev_rx, void *fwd,
3922 struct bpf_map *map, struct xdp_buff *xdp,
3923 u32 flags)
3924 {
3925 switch (map->map_type) {
3926 case BPF_MAP_TYPE_DEVMAP:
3927 case BPF_MAP_TYPE_DEVMAP_HASH:
> 3928 if (flags & BPF_F_REDIR_BROADCAST)
3929 return dev_map_enqueue_multi(xdp, dev_rx, map,
> 3930 flags & BPF_F_REDIR_EXCLUDE_INGRESS);
3931 else
3932 return dev_map_enqueue(fwd, xdp, dev_rx);
3933 case BPF_MAP_TYPE_CPUMAP:
3934 return cpu_map_enqueue(fwd, xdp, dev_rx);
3935 case BPF_MAP_TYPE_XSKMAP:
3936 return __xsk_map_redirect(fwd, xdp);
3937 default:
3938 return -EBADRQC;
3939 }
3940 return 0;
3941 }
3942
---
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: 14879 bytes --]
next prev parent reply other threads:[~2021-03-09 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 7:29 [PATCH bpf-next 0/4] xdp: extend xdp_redirect_map with broadcast support Hangbin Liu
2021-03-09 7:29 ` [PATCH bpf-next 1/4] bpf: run devmap xdp_prog on flush instead of bulk enqueue Hangbin Liu
2021-03-09 7:29 ` [PATCH bpf-next 2/4] xdp: extend xdp_redirect_map with broadcast support Hangbin Liu
2021-03-09 8:22 ` kernel test robot [this message]
2021-03-09 8:55 ` Hangbin Liu
2021-03-09 9:09 ` Daniel Borkmann
2021-03-09 9:53 ` Hangbin Liu
2021-03-09 7:29 ` [PATCH bpf-next 3/4] sample/bpf: add xdp_redirect_map_multi for redirect_map broadcast test Hangbin Liu
2021-03-09 7:29 ` [PATCH bpf-next 4/4] selftests/bpf: add xdp_redirect_multi test Hangbin Liu
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=202103091607.YXhmDMeL-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=echaudro@redhat.com \
--cc=jbenc@redhat.com \
--cc=kbuild-all@01.org \
--cc=liuhangbin@gmail.com \
--cc=lorenzo.bianconi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.com \
/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