From: kernel test robot <lkp@intel.com>
To: Sami Tolvanen <samitolvanen@google.com>,
bpf@vger.kernel.org, Puranjay Mohan <puranjay@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: oe-kbuild-all@lists.linux.dev,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Maxwell Bland <mbland@motorola.com>,
Sami Tolvanen <samitolvanen@google.com>
Subject: Re: [PATCH bpf-next v11 2/3] cfi: Move BPF CFI types and helpers to generic code
Date: Sun, 20 Jul 2025 07:32:18 +0800 [thread overview]
Message-ID: <202507200719.dWqamnJW-lkp@intel.com> (raw)
In-Reply-To: <20250718223345.1075521-7-samitolvanen@google.com>
Hi Sami,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 0ee30d937c147fc14c4b49535181d437cd2fde7a]
url: https://github.com/intel-lab-lkp/linux/commits/Sami-Tolvanen/cfi-add-C-CFI-type-macro/20250719-063535
base: 0ee30d937c147fc14c4b49535181d437cd2fde7a
patch link: https://lore.kernel.org/r/20250718223345.1075521-7-samitolvanen%40google.com
patch subject: [PATCH bpf-next v11 2/3] cfi: Move BPF CFI types and helpers to generic code
config: x86_64-randconfig-123-20250719 (https://download.01.org/0day-ci/archive/20250720/202507200719.dWqamnJW-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250720/202507200719.dWqamnJW-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/202507200719.dWqamnJW-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/cfi.c:39:24: sparse: sparse: symbol '__bpf_prog_runX' was not declared. Should it be static?
>> kernel/cfi.c:42:28: sparse: sparse: symbol '__bpf_callback_fn' was not declared. Should it be static?
vim +/__bpf_prog_runX +39 kernel/cfi.c
31
32 /*
33 * Declare two non-existent functions with types that match bpf_func_t and
34 * bpf_callback_t pointers, and use DEFINE_CFI_TYPE to define type hash
35 * variables for each function type. The cfi_bpf_* variables are used by
36 * arch-specific BPF JIT implementations to ensure indirectly callable JIT
37 * code has matching CFI type hashes.
38 */
> 39 typeof(*(bpf_func_t)0) __bpf_prog_runX;
40 DEFINE_CFI_TYPE(cfi_bpf_hash, __bpf_prog_runX);
41
> 42 typeof(*(bpf_callback_t)0) __bpf_callback_fn;
43 DEFINE_CFI_TYPE(cfi_bpf_subprog_hash, __bpf_callback_fn);
44
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-19 23:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 22:33 [PATCH bpf-next v11 0/3] Support kCFI + BPF on arm64 Sami Tolvanen
2025-07-18 22:33 ` [PATCH bpf-next v11 1/3] cfi: add C CFI type macro Sami Tolvanen
2025-07-18 22:33 ` [PATCH bpf-next v11 2/3] cfi: Move BPF CFI types and helpers to generic code Sami Tolvanen
2025-07-19 23:32 ` kernel test robot [this message]
2025-07-21 1:25 ` kernel test robot
2025-07-21 14:33 ` Will Deacon
2025-07-18 22:33 ` [PATCH bpf-next v11 3/3] arm64/cfi,bpf: Support kCFI + BPF on arm64 Sami Tolvanen
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=202507200719.dWqamnJW-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mbland@motorola.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=puranjay@kernel.org \
--cc=samitolvanen@google.com \
--cc=will@kernel.org \
/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®