Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Luis Gerhorst <luis.gerhorst@fau.de>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Puranjay Mohan <puranjay@kernel.org>,
	Xu Kuohai <xukuohai@huaweicloud.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Hari Bathini <hbathini@linux.ibm.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Naveen N Rao <naveen@kernel.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Mykola Lysenko <mykolal@fb.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Henriette Herzog <henriette.herzog@rub.de>,
	Saket Kumar Bhaskar <skb99@linux.ibm.com>,
	Cupertino Miranda <cupertino.miranda@oracle.com>,
	Jiayuan Chen <mrpre@163.com>,
	Matan Shachnai <m.shachnai@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH bpf-next v2 05/11] bpf, arm64, powerpc: Add bpf_jit_bypass_spec_v1/v4()
Date: Mon, 21 Apr 2025 20:26:00 +0800	[thread overview]
Message-ID: <202504212030.IF1SLhz6-lkp@intel.com> (raw)
In-Reply-To: <20250421091802.3234859-6-luis.gerhorst@fau.de>

Hi Luis,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 8582d9ab3efdebb88e0cd8beed8e0b9de76443e7]

url:    https://github.com/intel-lab-lkp/linux/commits/Luis-Gerhorst/selftests-bpf-Fix-caps-for-__xlated-jited_unpriv/20250421-175926
base:   8582d9ab3efdebb88e0cd8beed8e0b9de76443e7
patch link:    https://lore.kernel.org/r/20250421091802.3234859-6-luis.gerhorst%40fau.de
patch subject: [PATCH bpf-next v2 05/11] bpf, arm64, powerpc: Add bpf_jit_bypass_spec_v1/v4()
config: arm-randconfig-001-20250421 (https://download.01.org/0day-ci/archive/20250421/202504212030.IF1SLhz6-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250421/202504212030.IF1SLhz6-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/202504212030.IF1SLhz6-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> kernel/bpf/core.c:3037:13: warning: no previous prototype for function 'bpf_jit_bypass_spec_v1' [-Wmissing-prototypes]
    3037 | bool __weak bpf_jit_bypass_spec_v1(void)
         |             ^
   kernel/bpf/core.c:3037:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
    3037 | bool __weak bpf_jit_bypass_spec_v1(void)
         | ^
         | static 
>> kernel/bpf/core.c:3042:13: warning: no previous prototype for function 'bpf_jit_bypass_spec_v4' [-Wmissing-prototypes]
    3042 | bool __weak bpf_jit_bypass_spec_v4(void)
         |             ^
   kernel/bpf/core.c:3042:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
    3042 | bool __weak bpf_jit_bypass_spec_v4(void)
         | ^
         | static 
   2 warnings generated.


vim +/bpf_jit_bypass_spec_v1 +3037 kernel/bpf/core.c

  3031	
  3032	/* By default, enable the verifier's mitigations against Spectre v1 and v4 for
  3033	 * all archs. The value returned must not change at runtime as there is
  3034	 * currently no support for reloading programs that were loaded without
  3035	 * mitigations.
  3036	 */
> 3037	bool __weak bpf_jit_bypass_spec_v1(void)
  3038	{
  3039		return false;
  3040	}
  3041	
> 3042	bool __weak bpf_jit_bypass_spec_v4(void)
  3043	{
  3044		return false;
  3045	}
  3046	

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

           reply	other threads:[~2025-04-21 12:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20250421091802.3234859-6-luis.gerhorst@fau.de>]

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=202504212030.IF1SLhz6-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=cupertino.miranda@oracle.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=hbathini@linux.ibm.com \
    --cc=henriette.herzog@rub.de \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=luis.gerhorst@fau.de \
    --cc=m.shachnai@gmail.com \
    --cc=maddy@linux.ibm.com \
    --cc=martin.lau@linux.dev \
    --cc=mpe@ellerman.id.au \
    --cc=mrpre@163.com \
    --cc=mykolal@fb.com \
    --cc=naveen@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=puranjay@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=skb99@linux.ibm.com \
    --cc=skhan@linuxfoundation.org \
    --cc=song@kernel.org \
    --cc=will@kernel.org \
    --cc=xukuohai@huaweicloud.com \
    --cc=yonghong.song@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