[moderation/CI] Re: bpf: keep the vmlinux BTF compressed until first use (CONFIG_DEBUG_INFO_BTF_LAZY) to save ~6 MB memory

[moderation/CI] Re: bpf: keep the vmlinux BTF compressed until first use (CONFIG_DEBUG_INFO_BTF_LAZY) to save ~6 MB memory

[syzbot ci]

syzbot ci has tested the following series

[v1] bpf: keep the vmlinux BTF compressed until first use (CONFIG_DEBUG_INFO_BTF_LAZY) to save ~6 MB memory
https://lore.kernel.org/all/20261031130959.23472-1-wanjay@amazon.com
* [PATCH bpf-next 01/13] bpf: match program context types by name without vmlinux BTF
* [PATCH bpf-next 02/13] bpf: fetch the vmlinux BTF where kernel types enter a program
* [PATCH bpf-next 03/13] bpf: check CAP_SYS_ADMIN before looking up bpffs delegation names
* [PATCH bpf-next 04/13] bpf: move bpf_get_btf_vmlinux() to btf.c
* [PATCH bpf-next 05/13] bpf: let btf_parse_module() adopt the caller's copy of the module BTF
* [PATCH bpf-next 06/13] bpf: look up the struct_ops common value type in the given BTF
* [PATCH bpf-next 07/13] bpf: parse the vmlinux BTF before taking cand_cache_mutex
* [PATCH bpf-next 08/13] tracing: parse the vmlinux BTF when BTF-typed output is enabled
* [PATCH bpf-next 09/13] bpf: keep the vmlinux BTF zstd-compressed in the kernel image
* [PATCH bpf-next 10/13] bpf: defer kfunc and struct_ops registrations until first BTF use
* [PATCH bpf-next 11/13] bpf: keep module BTF until the vmlinux BTF is parsed
* [PATCH bpf-next 12/13] selftests/bpf: keep ksyms and linked_vars working without __start_BTF
* [PATCH bpf-next 13/13] Documentation/bpf: describe CONFIG_DEBUG_INFO_BTF_LAZY

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/a458b725-04a7-4acd-8bae-03303a203fc2

***

kernel build error

tree:      bpf-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base:      eaae576c34d7e001767b6845a5950b0b8db3e68a
arch:      amd64
compiler:  Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
config:    https://ci.syzbot.org/builds/4c72fd33-a422-4d38-8276-d463202193ff/config

./scripts/gen-btf.sh: 96: zstd: not found

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
  Tested-by: syzbot@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.

To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.

Notes:
- The patch will be applied on top of the tested series (as an
  incremental fix).
- To test a new version of the whole series, please send it directly
  to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.

The email will later be sent to:
[abuehaze@amazon.com almagui@kernel.org andrii@kernel.org arnd@arndb.de ast@kernel.org bpf@vger.kernel.org daniel@iogearbox.net doebel@amazon.de eddyz87@gmail.com ihor.solodrai@linux.dev jay.wang.upstream@gmail.com jolsa@kernel.org linux-arch@vger.kernel.org linux-doc@vger.kernel.org linux-kbuild@vger.kernel.org linux-kernel@vger.kernel.org linux-trace-kernel@vger.kernel.org martin.lau@linux.dev mathieu.desnoyers@efficios.com memxor@gmail.com mhiramat@kernel.org mpohlack@amazon.de nathan@kernel.org nsc@kernel.org rostedt@goodmis.org wanjay@amazon.com x86@kernel.org yonghong.song@linux.dev]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid