From: kbuild test robot <lkp@intel.com>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: arch/riscv/net/bpf_jit_comp.c:1662:47: error: 'BPF_JIT_REGION_START' undeclared; did you mean 'BPF_LWT_REROUTE'?
Date: Sat, 15 Feb 2020 13:30:54 +0800 [thread overview]
Message-ID: <202002151348.iW41gDAq%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]
Hi Björn,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 2019fc96af228b412bdb2e8e0ad4b1fc12046a51
commit: 7f3631e88ee6fb13beac333a0e9e605d2414d17f riscv, bpf: Provide RISC-V specific JIT image alloc/free
date: 8 weeks ago
config: riscv-randconfig-a001-20200215 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 7f3631e88ee6fb13beac333a0e9e605d2414d17f
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
arch/riscv/net/bpf_jit_comp.c: In function 'bpf_jit_alloc_exec':
>> arch/riscv/net/bpf_jit_comp.c:1662:47: error: 'BPF_JIT_REGION_START' undeclared (first use in this function); did you mean 'BPF_LWT_REROUTE'?
return __vmalloc_node_range(size, PAGE_SIZE, BPF_JIT_REGION_START,
^~~~~~~~~~~~~~~~~~~~
BPF_LWT_REROUTE
arch/riscv/net/bpf_jit_comp.c:1662:47: note: each undeclared identifier is reported only once for each function it appears in
>> arch/riscv/net/bpf_jit_comp.c:1663:9: error: 'BPF_JIT_REGION_END' undeclared (first use in this function); did you mean 'BPF_JIT_REGION_START'?
BPF_JIT_REGION_END, GFP_KERNEL,
^~~~~~~~~~~~~~~~~~
BPF_JIT_REGION_START
>> arch/riscv/net/bpf_jit_comp.c:1666:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
vim +1662 arch/riscv/net/bpf_jit_comp.c
1659
1660 void *bpf_jit_alloc_exec(unsigned long size)
1661 {
> 1662 return __vmalloc_node_range(size, PAGE_SIZE, BPF_JIT_REGION_START,
> 1663 BPF_JIT_REGION_END, GFP_KERNEL,
1664 PAGE_KERNEL_EXEC, 0, NUMA_NO_NODE,
1665 __builtin_return_address(0));
> 1666 }
1667
---
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: 29728 bytes --]
reply other threads:[~2020-02-15 5:31 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=202002151348.iW41gDAq%lkp@intel.com \
--to=lkp@intel.com \
--cc=bjorn.topel@gmail.com \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®