Netdev List
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Jiayuan Chen <jiayuan.chen@linux.dev>, acme@kernel.org
Cc: kuniyu@google.com, netdev@vger.kernel.org, llvm@lists.linux.dev,
	 ast@kernel.org, yonghong.song@linux.dev, bpf@vger.kernel.org,
	kuba@kernel.org,  tj@kernel.org
Subject: Re: [BUG] bpf: tcp: bpf_tcp_ops_set_rcvlowat() missing from BTF with clang KCSAN
Date: Fri, 6 Nov 2026 07:58:01 -0800	[thread overview]
Message-ID: <au347UiVUe5oUuxM@gmail.com> (raw)
In-Reply-To: <a69dd097-7e71-41f0-9a6b-eda001773236@linux.dev>

On Fri, Nov 06, 2026 at 09:16:24PM +0800, Jiayuan Chen wrote:
> Thanks for the report !
> 
> 
> On 11/6/26 7:38 PM, Breno Leitao wrote:
> > My arm64 KCSAN builds of linux-next fail since next-20261015, because
> > bpf_tcp_ops_set_rcvlowat() is missing from the vmlinux BTF:
> >
> >   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
> >   Try to disable CONFIG_DEBUG_INFO_BTF
> >   make[4]: *** [scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 1
> 
> 
> 
> Has pahole fixed this issue?

I don't think so, see the line below:

> > This is clang 22.1.3 and pahole 1.31 (current pahole master behaves the
> > same),

  reply	other threads:[~2026-11-06 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 11:38 [BUG] bpf: tcp: bpf_tcp_ops_set_rcvlowat() missing from BTF with clang KCSAN Breno Leitao
2026-11-06 13:16 ` Jiayuan Chen
2026-11-06 15:58   ` Breno Leitao [this message]
2026-11-06 19:05     ` Kuniyuki Iwashima
2026-11-09 12:33       ` Breno Leitao
2026-11-09 17:51         ` Arnaldo Carvalho de Melo
2026-11-10  5:40 ` netdev-bot+sashiko

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=au347UiVUe5oUuxM@gmail.com \
    --to=leitao@debian.org \
    --cc=acme@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=jiayuan.chen@linux.dev \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=llvm@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=tj@kernel.org \
    --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