Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Jeff Kirsher <jeff.kirsher@gmail.com>,
	Martin KaFai Lau <martin.lau@kernel.org>
Subject: [jkirsher-net-queue:master 4/4] arch/arm64/net/bpf_jit_comp.c:2258:6: warning: no previous prototype for function 'bpf_jit_supports_private_stack'
Date: Thu, 16 Oct 2025 04:57:58 +0800	[thread overview]
Message-ID: <202510160449.pcIYMJSz-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net-queue.git master
head:   c9a8544415241209a476e56cc98a09ab074e29a8
commit: c9a8544415241209a476e56cc98a09ab074e29a8 [4/4] bpf: Add support for certain atomics in bpf_arena to x86 JIT
config: arm64-randconfig-004-20251016 (https://download.01.org/0day-ci/archive/20251016/202510160449.pcIYMJSz-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 39f292ffa13d7ca0d1edff27ac8fd55024bb4d19)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251016/202510160449.pcIYMJSz-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202510160449.pcIYMJSz-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> arch/arm64/net/bpf_jit_comp.c:2258:6: warning: no previous prototype for function 'bpf_jit_supports_private_stack' [-Wmissing-prototypes]
    2258 | bool bpf_jit_supports_private_stack(void)
         |      ^
   arch/arm64/net/bpf_jit_comp.c:2258:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
    2258 | bool bpf_jit_supports_private_stack(void)
         | ^
         | static 
>> arch/arm64/net/bpf_jit_comp.c:3096:6: warning: no previous prototype for function 'bpf_jit_supports_timed_may_goto' [-Wmissing-prototypes]
    3096 | bool bpf_jit_supports_timed_may_goto(void)
         |      ^
   arch/arm64/net/bpf_jit_comp.c:3096:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
    3096 | bool bpf_jit_supports_timed_may_goto(void)
         | ^
         | static 
   2 warnings generated.


vim +/bpf_jit_supports_private_stack +2258 arch/arm64/net/bpf_jit_comp.c

91fc957c9b1d6c5 Ard Biesheuvel 2018-11-23  2257  
6c17a882d3804dc Puranjay Mohan 2025-07-24 @2258  bool bpf_jit_supports_private_stack(void)
6c17a882d3804dc Puranjay Mohan 2025-07-24  2259  {
6c17a882d3804dc Puranjay Mohan 2025-07-24  2260  	return true;
6c17a882d3804dc Puranjay Mohan 2025-07-24  2261  }
6c17a882d3804dc Puranjay Mohan 2025-07-24  2262  

:::::: The code at line 2258 was first introduced by commit
:::::: 6c17a882d3804dce1c66e1fec25f96d39a184067 bpf, arm64: JIT support for private stack

:::::: TO: Puranjay Mohan <puranjay@kernel.org>
:::::: CC: Daniel Borkmann <daniel@iogearbox.net>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-10-15 20:58 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=202510160449.pcIYMJSz-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ast@kernel.org \
    --cc=jeff.kirsher@gmail.com \
    --cc=llvm@lists.linux.dev \
    --cc=martin.lau@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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