From: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>
To: "Jakub Kicinski" <kuba@kernel.org>, <chia-yu.chang@nokia-bell-labs.com>
Cc: <john.fastabend@gmail.com>, <jakub@cloudflare.com>,
<jiayuan.chen@linux.dev>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>,
<andrii@kernel.org>, <eddyz87@gmail.com>, <martin.lau@linux.dev>,
<song@kernel.org>, <yonghong.song@linux.dev>, <jolsa@kernel.org>,
<emil@etsalapatis.com>, <linux-kselftest@vger.kernel.org>,
<shuah@kernel.org>, <horms@kernel.org>, <dsahern@kernel.org>,
<pabeni@redhat.com>, <jhs@mojatatu.com>,
<stephen@networkplumber.org>, <davem@davemloft.net>,
<edumazet@google.com>, <andrew+netdev@lunn.ch>,
<donald.hunter@gmail.com>, <kuniyu@google.com>, <ij@kernel.org>,
<ncardwell@google.com>, <koen.de_schepper@nokia-bell-labs.com>,
<g.white@cablelabs.com>, <ingemar.s.johansson@ericsson.com>,
<mirja.kuehlewind@ericsson.com>, <cheshire@apple.com>,
<rs.ietf@gmx.at>, <Jason_Livingood@comcast.com>,
<vidhi_goel@apple.com>, <Mike_Rudolph@comcast.com>,
<Jeff_Howe@comcast.com>, <srichard@netapp.com>
Subject: Re: [PATCH v8 net-next 0/2] Explicit TSO segment count
Date: Mon, 24 Aug 2026 22:09:52 +0200 [thread overview]
Message-ID: <DKXG3AFFUMEJ.1RDMQ7LNT1D0S@gmail.com> (raw)
In-Reply-To: <20260824130511.2955f30d@kernel.org>
On Mon Aug 24, 2026 at 10:05 PM CEST, Jakub Kicinski wrote:
> On Mon, 24 Aug 2026 18:31:37 +0200 chia-yu.chang@nokia-bell-labs.com
> wrote:
>> From: Chia-Yu Chang <chia-yu.chang@nokia-bell-labs.com>
>>
>> Hello,
>>
>> This series replaces the existing min_tso_segs() congestion control
>> callback with a new tso_segs() callback that allows congestion control
>> algorithms to provide an explicit TSO segment count for each data burst.
>>
>> To support BPF congestion controls, the series also exposes
>> tcp_tso_autosize() as a BPF kfunc, allowing BPF implementations to
>> reuse the kernel TSO autosizing logic while implementing custom
>> tso_segs() callbacks.
>
> AI CI says:
>
> The bpf-ci build jobs are failing for this patch on all tested
> architectures/toolchains (x86-64 gcc-15, x86-64 llvm-21, aarch64 gcc-15,
> s390x gcc-15), all with the same link-time error:
>
> net/ipv4/tcp_bbr.o: in function `__BTF_ID__set8__tcp_bbr_check_kfunc_ids':
> tcp_bbr.c:(.BTF_ids+0x...): undefined reference to `KF_DEPRECATED'
>
> This comes from the change to net/ipv4/tcp_bbr.c that marks the retained
> bbr_min_tso_segs() kfunc entry with the KF_DEPRECATED flag:
>
> BTF_ID_FLAGS(func, bbr_min_tso_segs, KF_DEPRECATED)
> BTF_ID_FLAGS(func, bbr_tso_segs)
>
> KF_DEPRECATED does not resolve to a usable symbol/flag in this tree, so
> the BTF id set for tcp_bbr fails to link into vmlinux on every
> architecture and toolchain -- it's a straight undefined-reference error,
> not a per-arch/per-config issue.
>
> Could you drop the KF_DEPRECATED flag (or use a flag that this kfunc
> infrastructure actually defines) on bbr_min_tso_segs, and re-verify that
> the kernel links cleanly? A local `make net/ipv4/tcp_bbr.o vmlinux`
> build (or the bpf-ci selftest build job) should reproduce this quickly.
>
> Full build log for reference:
>
> ld.lld-21: error: undefined symbol: KF_DEPRECATED
> >>> referenced by usercopy_64.c
> >>> vmlinux.o:(__BTF_ID__set8__tcp_bbr_check_kfunc_ids)
I think Chia-Yu's AI is hallucinating, it was a proposed flag but not added yet...
next prev parent reply other threads:[~2026-08-24 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 16:31 [PATCH v8 net-next 0/2] Explicit TSO segment count chia-yu.chang
2026-08-24 16:31 ` [PATCH v8 net-next 1/2] tcp: Replace min_tso_segs() with tso_segs() CC callback chia-yu.chang
2026-08-24 16:31 ` [PATCH v8 net-next 2/2] bpf: make tcp_tso_autosize() available to BPF congestion controls chia-yu.chang
2026-08-24 18:08 ` [PATCH v8 net-next 0/2] Explicit TSO segment count Jakub Kicinski
2026-08-24 20:05 ` Jakub Kicinski
2026-08-24 20:09 ` Kumar Kartikeya Dwivedi [this message]
2026-08-24 20:21 ` Chia-Yu Chang (Nokia)
2026-08-24 20:26 ` Kumar Kartikeya Dwivedi
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=DKXG3AFFUMEJ.1RDMQ7LNT1D0S@gmail.com \
--to=memxor@gmail.com \
--cc=Jason_Livingood@comcast.com \
--cc=Jeff_Howe@comcast.com \
--cc=Mike_Rudolph@comcast.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cheshire@apple.com \
--cc=chia-yu.chang@nokia-bell-labs.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=emil@etsalapatis.com \
--cc=g.white@cablelabs.com \
--cc=horms@kernel.org \
--cc=ij@kernel.org \
--cc=ingemar.s.johansson@ericsson.com \
--cc=jakub@cloudflare.com \
--cc=jhs@mojatatu.com \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=koen.de_schepper@nokia-bell-labs.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mirja.kuehlewind@ericsson.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rs.ietf@gmx.at \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=srichard@netapp.com \
--cc=stephen@networkplumber.org \
--cc=vidhi_goel@apple.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