BPF List
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Alan Maguire <almagui@kernel.org>
Cc: Yonghong Song <yonghong.song@linux.dev>,
	 Alan Maguire <alan.maguire@oracle.com>,
	Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	 dwarves@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
	 Andrii Nakryiko <andrii@kernel.org>,
	bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH dwarves] btf_encoder: Keep the source prototype of kfuncs
Date: Thu, 12 Nov 2026 05:54:38 -0800	[thread overview]
Message-ID: <avXE70_JpiqemxzV@gmail.com> (raw)
In-Reply-To: <ffd8e847-6a3f-4403-a33c-1b3804e1c039@kernel.org>

Hello Alan,

On Thu, Nov 12, 2026 at 12:36:29PM +0000, Alan Maguire wrote:
> > Reported-by: Breno Leitao <leitao@debian.org>
> 
> I'm having trouble reproducing the original failure; would you mind sharing
> the config that reproduces it? I tried with clang 22, but no luck so far.

This reproduces it on x86_64, with next-20261111, clang 22.1.3 and
pahole master (9eb594d):

    # make LLVM=1 x86_64_defconfig
    # ./scripts/config -e BPF_SYSCALL -e BPF_JIT -e CGROUP_BPF \
            -d DEBUG_INFO_NONE -e DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT \
            -e DEBUG_INFO_BTF -e KCSAN -e UBSAN -e WERROR
    # make LLVM=1 olddefconfig
    # make LLVM=1 -j$(nproc) vmlinux
    [...]
      BTF     .tmp_vmlinux1
    WARN: resolve_btfids: no BTF func for kfunc bpf_tcp_ops_set_rcvlowat in bpf_tcp_ops_set_rcvlowat_kfunc_set
    WARN: resolve_btfids: unresolved symbol bpf_tcp_ops_set_rcvlowat
    Failed to generate BTF for vmlinux

let me know if you are not able to, and I will send you my full .config

Thanks,
--breno

  reply	other threads:[~2026-11-12 13:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 22:24 [PATCH dwarves] btf_encoder: Keep the source prototype of kfuncs Yonghong Song
2026-11-12 10:53 ` Breno Leitao
2026-11-12 12:36 ` Alan Maguire
2026-11-12 13:54   ` Breno Leitao [this message]
2026-11-12 15:26   ` Yonghong Song

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=avXE70_JpiqemxzV@gmail.com \
    --to=leitao@debian.org \
    --cc=alan.maguire@oracle.com \
    --cc=almagui@kernel.org \
    --cc=andrii@kernel.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=dwarves@vger.kernel.org \
    --cc=kernel-team@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox