From: Daniel Borkmann <daniel@iogearbox.net>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
bjorn@kernel.org
Subject: Re: arch/x86/net/bpf_jit_comp.c:2188:5: warning: no previous prototype for 'arch_prepare_bpf_dispatcher'
Date: Tue, 16 Nov 2021 10:03:58 +0100 [thread overview]
Message-ID: <74c60313-699a-2e3b-af36-49387cfadae3@iogearbox.net> (raw)
In-Reply-To: <202111161117.ZvVGmBJV-lkp@intel.com>
[ Cc Bjorn ]
On 11/16/21 4:25 AM, kernel test robot wrote:
> Hi Daniel,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 8ab774587903771821b59471cc723bba6d893942
> commit: b24abcff918a5cbf44b0c982bd3477a93e8e4911 bpf, kconfig: Add consolidated menu entry for bpf with core options
> date: 6 months ago
> config: x86_64-buildonly-randconfig-r006-20211012 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b24abcff918a5cbf44b0c982bd3477a93e8e4911
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout b24abcff918a5cbf44b0c982bd3477a93e8e4911
> # save the attached .config to linux build tree
> make W=1 ARCH=x86_64
>
> 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/x86/net/bpf_jit_comp.c:2188:5: warning: no previous prototype for 'arch_prepare_bpf_dispatcher' [-Wmissing-prototypes]
> 2188 | int arch_prepare_bpf_dispatcher(void *image, s64 *funcs, int num_funcs)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> vim +/arch_prepare_bpf_dispatcher +2188 arch/x86/net/bpf_jit_comp.c
>
> 75ccbef6369e94 Björn Töpel 2019-12-13 2187
> 75ccbef6369e94 Björn Töpel 2019-12-13 @2188 int arch_prepare_bpf_dispatcher(void *image, s64 *funcs, int num_funcs)
> 75ccbef6369e94 Björn Töpel 2019-12-13 2189 {
> 75ccbef6369e94 Björn Töpel 2019-12-13 2190 u8 *prog = image;
> 75ccbef6369e94 Björn Töpel 2019-12-13 2191
> 75ccbef6369e94 Björn Töpel 2019-12-13 2192 sort(funcs, num_funcs, sizeof(funcs[0]), cmp_ips, NULL);
> 75ccbef6369e94 Björn Töpel 2019-12-13 2193 return emit_bpf_dispatcher(&prog, 0, num_funcs - 1, funcs);
> 75ccbef6369e94 Björn Töpel 2019-12-13 2194 }
> 75ccbef6369e94 Björn Töpel 2019-12-13 2195
>
> :::::: The code at line 2188 was first introduced by commit
> :::::: 75ccbef6369e94ecac696a152a998a978d41376b bpf: Introduce BPF dispatcher
>
> :::::: TO: Björn Töpel <bjorn.topel@intel.com>
> :::::: CC: Alexei Starovoitov <ast@kernel.org>
>
> ---
> 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-11-16 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 3:25 arch/x86/net/bpf_jit_comp.c:2188:5: warning: no previous prototype for 'arch_prepare_bpf_dispatcher' kernel test robot
2021-11-16 9:03 ` 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=74c60313-699a-2e3b-af36-49387cfadae3@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).