From: kernel test robot <lkp@intel.com>
To: Justin Suess <utilityemal77@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>
Subject: kernel/bpf/verifier.c:2276:19: error: use of undeclared identifier 'bpf_landlock_ruleset_btf_ids'
Date: Wed, 08 Apr 2026 09:18:00 +0200 [thread overview]
Message-ID: <202604080920.Cm9eXBu4-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Justin-Suess/landlock-Move-operations-from-syscall-into-ruleset-code/20260408-053705
head: 7423cdaa89895ef6399743cfef9c7bfe1c22b8ad
commit: a0c8fd8936e1475411b42961f95d16772832b543 bpf: verifier: Add Landlock ruleset map support
date: 10 hours ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260408/202604080920.Cm9eXBu4-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/20260408/202604080920.Cm9eXBu4-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/202604080920.Cm9eXBu4-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/bpf/verifier.c:2276:19: error: use of undeclared identifier 'bpf_landlock_ruleset_btf_ids'
2276 | reg->btf_id = *bpf_landlock_ruleset_btf_ids;
| ^
1 error generated.
vim +/bpf_landlock_ruleset_btf_ids +2276 kernel/bpf/verifier.c
2252
2253 static void mark_ptr_not_null_reg(struct bpf_reg_state *reg)
2254 {
2255 if (base_type(reg->type) == PTR_TO_MAP_VALUE) {
2256 const struct bpf_map *map = reg->map_ptr;
2257
2258 if (map->inner_map_meta) {
2259 reg->type = CONST_PTR_TO_MAP;
2260 reg->map_ptr = map->inner_map_meta;
2261 /* transfer reg's id which is unique for every map_lookup_elem
2262 * as UID of the inner map.
2263 */
2264 if (btf_record_has_field(map->inner_map_meta->record,
2265 BPF_TIMER | BPF_WORKQUEUE | BPF_TASK_WORK)) {
2266 reg->map_uid = reg->id;
2267 }
2268 } else if (map->map_type == BPF_MAP_TYPE_XSKMAP) {
2269 reg->type = PTR_TO_XDP_SOCK;
2270 } else if (map->map_type == BPF_MAP_TYPE_SOCKMAP ||
2271 map->map_type == BPF_MAP_TYPE_SOCKHASH) {
2272 reg->type = PTR_TO_SOCKET;
2273 } else if (map->map_type == BPF_MAP_TYPE_LANDLOCK_RULESET) {
2274 reg->type = PTR_TO_BTF_ID | PTR_TRUSTED;
2275 reg->btf = btf_vmlinux;
> 2276 reg->btf_id = *bpf_landlock_ruleset_btf_ids;
2277 } else {
2278 reg->type = PTR_TO_MAP_VALUE;
2279 }
2280 return;
2281 }
2282
2283 reg->type &= ~PTR_MAYBE_NULL;
2284 }
2285
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-08 7:18 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=202604080920.Cm9eXBu4-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=utilityemal77@gmail.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