From: Daniel Borkmann <daniel@iogearbox.net>
To: kernel test robot <lkp@intel.com>, Tong Tiangen <tongtiangen@huawei.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
bjorn@kernel.org
Subject: Re: [linux-next:master 11855/12471] arch/riscv/net/bpf_jit_comp64.c:462:5: warning: no previous prototype for function 'rv_bpf_fixup_exception'
Date: Thu, 28 Oct 2021 21:58:23 +0200 [thread overview]
Message-ID: <0d291bf9-af19-9658-8b58-0ec814dba6d6@iogearbox.net> (raw)
In-Reply-To: <202110290334.2zdMyRq4-lkp@intel.com>
[ +Bjorn ]
On 10/28/21 9:45 PM, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 503f375baa99edff894eb1a534d2ac0b4f799573
> commit: 252c765bd764a246a8bd516fabf6d6123df4a24f [11855/12471] riscv, bpf: Add BPF exception tables
> config: riscv-randconfig-r042-20211028 (attached as .config)
> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 5db7568a6a1fcb408eb8988abdaff2a225a8eb72)
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # install riscv cross compiling tool for clang build
> # apt-get install binutils-riscv64-linux-gnu
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=252c765bd764a246a8bd516fabf6d6123df4a24f
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 252c765bd764a246a8bd516fabf6d6123df4a24f
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=riscv
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
>>> arch/riscv/net/bpf_jit_comp64.c:462:5: warning: no previous prototype for function 'rv_bpf_fixup_exception' [-Wmissing-prototypes]
> int rv_bpf_fixup_exception(const struct exception_table_entry *ex,
> ^
> arch/riscv/net/bpf_jit_comp64.c:462:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
> int rv_bpf_fixup_exception(const struct exception_table_entry *ex,
> ^
> static
> 1 warning generated.
Tong, Bjorn, ptal
> vim +/rv_bpf_fixup_exception +462 arch/riscv/net/bpf_jit_comp64.c
>
> 461
> > 462 int rv_bpf_fixup_exception(const struct exception_table_entry *ex,
> 463 struct pt_regs *regs)
> 464 {
> 465 off_t offset = FIELD_GET(BPF_FIXUP_OFFSET_MASK, ex->fixup);
> 466 int regs_offset = FIELD_GET(BPF_FIXUP_REG_MASK, ex->fixup);
> 467
> 468 *(unsigned long *)((void *)regs + pt_regmap[regs_offset]) = 0;
> 469 regs->epc = (unsigned long)&ex->fixup - offset;
> 470
> 471 return 1;
> 472 }
> 473
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
prev parent reply other threads:[~2021-10-28 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 19:45 kernel test robot
2021-10-28 19:58 ` Daniel Borkmann [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=0d291bf9-af19-9658-8b58-0ec814dba6d6@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=bjorn@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=tongtiangen@huawei.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