From: "Arthur Fabre" <afabre@cloudflare.com>
To: "Martin KaFai Lau" <martin.lau@linux.dev>
Cc: <daniel@iogearbox.net>, <john.fastabend@gmail.com>,
<sdf@fomichev.me>, <ast@kernel.org>, <andrii@kernel.org>,
<eddyz87@gmail.com>, <song@kernel.org>, <yonghong.song@linux.dev>,
<kpsingh@kernel.org>, <haoluo@google.com>, <jolsa@kernel.org>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <horms@kernel.org>, <bpf@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel-team@cloudflare.com>, <wferguson@cloudflare.com>,
<martin.lau@kernel.org>, <clm@meta.com>,
<ihor.solodrai@linux.dev>, <bot+bpf-ci@kernel.org>
Subject: Re: [PATCH bpf-next] bpf: Allow bpf_tcp_sock() helper in XDP
Date: Thu, 05 Feb 2026 16:52:27 +0100 [thread overview]
Message-ID: <DG75D8PWP35E.2MD9TYHOCQO9V@cloudflare.com> (raw)
In-Reply-To: <917eadc0-9341-48d5-a795-8a7d5318886c@linux.dev>
On Wed Feb 4, 2026 at 11:27 PM CET, Martin KaFai Lau wrote:
>
>
> On 2/4/26 5:04 AM, bot+bpf-ci@kernel.org wrote:
> >> But the TCP TIME-WAIT state needs special handling for this: packets
> >> received for a TIME-WAIT socket can either belong to the current
> >> incarnation of the connection, or a new incarnation. The only way to
> >> determine this is to compare the sequence numbers.
> >>
> >> Add the bpf_tcp_sock() helper in XDP to allow the socket sequence
> >> numbers to be read.
> >
> > Can this approach work for TIME-WAIT sockets? Looking at bpf_tcp_sock() in
> > net/core/filter.c:
> >
> > if (sk_fullsock(sk) && sk->sk_protocol == IPPROTO_TCP)
> > return (unsigned long)sk;
> > return (unsigned long)NULL;
> >
> > And sk_fullsock() in include/net/sock.h:
> >
> > static inline bool sk_fullsock(const struct sock *sk)
> > {
> > return (1 << sk->sk_state) & ~(TCPF_TIME_WAIT | TCPF_NEW_SYN_RECV);
> > }
> >
> > TIME-WAIT sockets are explicitly excluded by sk_fullsock(), so bpf_tcp_sock()
> > returns NULL for them. The sequence numbers stored in TIME-WAIT sockets
> > (skc_tw_rcv_nxt and skc_tw_snd_nxt in sock_common) would not be accessible
> > through this helper.
> >
> > The change itself is useful for accessing tcp_sock fields from established
> > connections in XDP, but the commit message implies this solves the TIME-WAIT
> > sequence number problem described, which doesn't appear to be the case.
>
> or use "tp = bpf_core_cast(sk, struct tcp_sock /* or tcp_timewait_sock
> */);". The bpf prog can also read all members of the kernel struct
> instead of a subset defined in bpf_tcp_sock.
Brilliant, that works! Thanks Martin.
>
> pw-bot: cr
>
> >
> >
> > ---
> > AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
> > See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
> >
> > CI run summary: https://github.com/kernel-patches/bpf/actions/runs/21671977729
> >
> > AI-authorship-score: low
> > AI-authorship-explanation: The commit message style is consistent with human-written kernel patches, with natural technical language and standard formatting; the technical error is more likely human oversight than AI hallucination.
> > issues-found: 1
> > issue-severity-score: low
> > issue-severity-explanation: The issue is a misleading commit message that claims the change enables TIME-WAIT socket sequence number reading, but the bpf_tcp_sock() helper explicitly returns NULL for TIME-WAIT sockets.
prev parent reply other threads:[~2026-02-05 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 12:24 [PATCH bpf-next] bpf: Allow bpf_tcp_sock() helper in XDP Arthur Fabre
2026-02-04 13:04 ` bot+bpf-ci
2026-02-04 22:27 ` Martin KaFai Lau
2026-02-05 15:52 ` Arthur Fabre [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=DG75D8PWP35E.2MD9TYHOCQO9V@cloudflare.com \
--to=afabre@cloudflare.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=horms@kernel.org \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@cloudflare.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=wferguson@cloudflare.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