From: kernel test robot <lkp@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
" Łukasz Bartosik" <ukaszb@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:folio-pool-v2-lockdep 6/21] kernel/bpf/verifier.c:19799:27: error: incompatible pointer types passing 'struct static_key_true *' to parameter of type 'struct static_key *'
Date: Tue, 18 Aug 2026 17:20:46 +0800 [thread overview]
Message-ID: <202608181709.ruVYmi71-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git folio-pool-v2-lockdep
head: e77ee8289ea0755b0ee299348504d4568f942d71
commit: ae43aea8c1fa99e61d57341384a5f99c293d1f5f [6/21] bpf/verifier: Route verifier stack state node allocations to folio_pool
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20260818/202608181709.ruVYmi71-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 844a18e753e822736c9805ab779144b647a2c186)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260818/202608181709.ruVYmi71-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/202608181709.ruVYmi71-lkp@intel.com/
Note: the jimc/folio-pool-v2-lockdep HEAD e77ee8289ea0755b0ee299348504d4568f942d71 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> kernel/bpf/verifier.c:19799:27: error: incompatible pointer types passing 'struct static_key_true *' to parameter of type 'struct static_key *' [-Wincompatible-pointer-types]
19799 | get_order(SZ_64K), &bpf_state_pool_key);
| ^~~~~~~~~~~~~~~~~~~
include/linux/folio_pool.h:240:24: note: passing argument to parameter 'key' here
240 | struct static_key *key);
| ^
1 error generated.
vim +19799 kernel/bpf/verifier.c
19776
19777 int bpf_check(struct bpf_prog **prog, union bpf_attr *attr, bpfptr_t uattr,
19778 struct bpf_log_attr *attr_log)
19779 {
19780 u64 start_time = ktime_get_ns();
19781 struct bpf_verifier_env *env;
19782 int i, len, ret = -EINVAL, err;
19783 bool is_priv;
19784
19785 BTF_TYPE_EMIT(enum bpf_features);
19786
19787 /* no program is valid */
19788 if (ARRAY_SIZE(bpf_verifier_ops) == 0)
19789 return -EINVAL;
19790
19791 /* 'struct bpf_verifier_env' can be global, but since it's not small,
19792 * allocate/free it every time bpf_check() is called
19793 */
19794 env = kvzalloc_obj(struct bpf_verifier_env, GFP_KERNEL_ACCOUNT);
19795 if (!env)
19796 return -ENOMEM;
19797
19798 folio_pool_init_key(&env->state_pool, sizeof(struct bpf_verifier_stack_elem),
19799 get_order(SZ_64K), &bpf_state_pool_key);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-18 9:21 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=202608181709.ruVYmi71-lkp@intel.com \
--to=lkp@intel.com \
--cc=jim.cromie@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ukaszb@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.