From: patchwork-bot+netdevbpf@kernel.org
To: Sasha Levin <sashal@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
ihor.solodrai@linux.dev, edumazet@kernel.org, kuniyu@google.com,
pabeni@redhat.com, willemb@google.com, davem@davemloft.net,
kuba@kernel.org, horms@kernel.org, ameryhung@gmail.com,
puranjay@kernel.org, sdf@fomichev.me, mahe.tardy@gmail.com,
jiayuan.chen@linux.dev, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, petr.pavlu@suse.com,
leon.hwang@linux.dev
Subject: Re: [PATCH bpf-next 0/3] bpf: Fix builds broken by fatal resolve_btfids warnings
Date: Tue, 20 Oct 2026 00:20:11 +0000 [thread overview]
Message-ID: <179245561140.3398635.15879772378050778401.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261019211006.2574350-1-sashal@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 19 Oct 2026 17:10:03 -0400 you wrote:
> Commit 201a454df948 ("resolve_btfids: Fix the --fatal_warnings exit
> status") makes resolve_btfids warnings fail the build again with
> CONFIG_WERROR=y. That exposed BTF ID references to functions some
> configs don't build. KernelCI has been seeing i386
> i386_defconfig+kselftest builds fail on linux-next since next-20261015:
>
> WARN: resolve_btfids: unresolved symbol bpf_arena_reserve_pages
> WARN: resolve_btfids: unresolved symbol bpf_arena_free_pages
> WARN: resolve_btfids: unresolved symbol bpf_arena_alloc_pages
> Failed to generate BTF for vmlinux
> Try to disable CONFIG_DEBUG_INFO_BTF
>
> [...]
Here is the summary with links:
- [bpf-next,1/3] bpf: Drop unused entries from special_kfunc_list again
https://git.kernel.org/bpf/bpf-next/c/63be110a96ae
- [bpf-next,2/3] bpf: Don't reference arena kfuncs when arena isn't built
https://git.kernel.org/bpf/bpf-next/c/ced6a0993e2f
- [bpf-next,3/3] bpf: Fix ksock build with BPF_LSM=y and SECURITY_NETWORK=n
https://git.kernel.org/bpf/bpf-next/c/a81bd9262cde
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-20 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 21:10 [PATCH bpf-next 0/3] bpf: Fix builds broken by fatal resolve_btfids warnings Sasha Levin
2026-10-19 21:10 ` [PATCH bpf-next 1/3] bpf: Drop unused entries from special_kfunc_list again Sasha Levin
2026-10-19 21:10 ` [PATCH bpf-next 2/3] bpf: Don't reference arena kfuncs when arena isn't built Sasha Levin
2026-10-19 21:10 ` [PATCH bpf-next 3/3] bpf: Fix ksock build with BPF_LSM=y and SECURITY_NETWORK=n Sasha Levin
2026-10-19 23:16 ` Mahe Tardy
2026-10-20 0:20 ` patchwork-bot+netdevbpf [this message]
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=179245561140.3398635.15879772378050778401.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@kernel.org \
--cc=emil@etsalapatis.com \
--cc=horms@kernel.org \
--cc=ihor.solodrai@linux.dev \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mahe.tardy@gmail.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petr.pavlu@suse.com \
--cc=puranjay@kernel.org \
--cc=sashal@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=willemb@google.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 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.