From: Daniel Borkmann <daniel@iogearbox.net>
To: kernel test robot <lkp@intel.com>, Yan Zhu <zhuyan34@huawei.com>
Cc: kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org
Subject: Re: [ammarfaizi2-block:bpf/bpf-next/pr/bpf-sysctl 1/1] kernel/bpf/syscall.c:4944:13: warning: no previous prototype for 'unpriv_ebpf_notify'
Date: Thu, 14 Apr 2022 00:51:17 +0200 [thread overview]
Message-ID: <bb65135e-035b-b82e-f75c-236a4ec72923@iogearbox.net> (raw)
In-Reply-To: <202204140614.Tt9e1fIt-lkp@intel.com>
On 4/14/22 12:42 AM, kernel test robot wrote:
> tree: https://github.com/ammarfaizi2/linux-block bpf/bpf-next/pr/bpf-sysctl
> head: 2900005ea287b11dcc8c1b9fcf24893b7ff41d6d
> commit: 2900005ea287b11dcc8c1b9fcf24893b7ff41d6d [1/1] bpf: Move BPF sysctls from kernel/sysctl.c to BPF core
> config: sh-buildonly-randconfig-r001-20220413 (https://download.01.org/0day-ci/archive/20220414/202204140614.Tt9e1fIt-lkp@intel.com/config)
> compiler: sh4-linux-gcc (GCC) 11.2.0
> 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
> # https://github.com/ammarfaizi2/linux-block/commit/2900005ea287b11dcc8c1b9fcf24893b7ff41d6d
> git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
> git fetch --no-tags ammarfaizi2-block bpf/bpf-next/pr/bpf-sysctl
> git checkout 2900005ea287b11dcc8c1b9fcf24893b7ff41d6d
> # save the config file to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=sh SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All error/warnings (new ones prefixed by >>):
>
> sh4-linux-ld: arch/sh/lib/mcount.o: in function `stack_panic':
>>> (.text+0x50): undefined reference to `dump_stack'
> --
>>> kernel/bpf/syscall.c:4944:13: warning: no previous prototype for 'unpriv_ebpf_notify' [-Wmissing-prototypes]
> 4944 | void __weak unpriv_ebpf_notify(int new_state)
> | ^~~~~~~~~~~~~~~~~~
>
>
> vim +/unpriv_ebpf_notify +4944 kernel/bpf/syscall.c
>
> 4943
>> 4944 void __weak unpriv_ebpf_notify(int new_state)
> 4945 {
> 4946 }
> 4947
>
(Note that this is no different than the way it was before wrt prototype.)
prev parent reply other threads:[~2022-04-13 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 22:42 kernel test robot
2022-04-13 22:51 ` 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=bb65135e-035b-b82e-f75c-236a4ec72923@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=zhuyan34@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
all inboxes | Powered by JetHome®