* [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
@ 2025-07-21 3:16 fan.yu9
2025-07-22 0:13 ` Jakub Kicinski
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: fan.yu9 @ 2025-07-21 3:16 UTC (permalink / raw)
To: kuba, edumazet, ncardwell, davem, dsahern, pabeni, horms, kuniyu,
rostedt, mhiramat, mathieu.desnoyers
Cc: netdev, linux-kernel, linux-trace-kernel, yang.yang29, xu.xin16,
tu.qiang35, jiang.kun2, qiu.yutan, wang.yaxin, he.peilin
From: Fan Yu <fan.yu9@zte.com.cn>
Background
==========
When TCP retransmits a packet due to missing ACKs, the
retransmission may fail for various reasons (e.g., packets
stuck in driver queues, receiver zero windows, or routing issues).
The original tcp_retransmit_skb tracepoint:
'commit e086101b150a ("tcp: add a tracepoint for tcp retransmission")'
lacks visibility into these failure causes, making production
diagnostics difficult.
Solution
========
Adds the retval("err") to the tcp_retransmit_skb tracepoint.
Enables users to know why some tcp retransmission failed and
users can filter retransmission failures by retval.
Compatibility description
=========================
This patch extends the tcp_retransmit_skb tracepoint
by adding a new "err" field at the end of its
existing structure (within TP_STRUCT__entry). The
compatibility implications are detailed as follows:
1) Structural compatibility for legacy user-space tools
Legacy tools/BPF programs accessing existing fields
(by offset or name) can still work without modification
or recompilation.The new field is appended to the end,
preserving original memory layout.
2) Note: semantic changes
The original tracepoint primarily only focused on
successfully retransmitted packets. With this patch,
the tracepoint now can figure out packets that may
terminate early due to specific reasons. For accurate
statistics, users should filter using "err" to
distinguish outcomes.
Before patched:
# cat /sys/kernel/debug/tracing/events/tcp/tcp_retransmit_skb/format
field:const void * skbaddr; offset:8; size:8; signed:0;
field:const void * skaddr; offset:16; size:8; signed:0;
field:int state; offset:24; size:4; signed:1;
field:__u16 sport; offset:28; size:2; signed:0;
field:__u16 dport; offset:30; size:2; signed:0;
field:__u16 family; offset:32; size:2; signed:0;
field:__u8 saddr[4]; offset:34; size:4; signed:0;
field:__u8 daddr[4]; offset:38; size:4; signed:0;
field:__u8 saddr_v6[16]; offset:42; size:16; signed:0;
field:__u8 daddr_v6[16]; offset:58; size:16; signed:0;
print fmt: "skbaddr=%p skaddr=%p family=%s sport=%hu dport=%hu saddr=%pI4 daddr=%pI4 saddrv6=%pI6c daddrv6=%pI6c state=%s"
After patched:
# cat /sys/kernel/debug/tracing/events/tcp/tcp_retransmit_skb/format
field:const void * skbaddr; offset:8; size:8; signed:0;
field:const void * skaddr; offset:16; size:8; signed:0;
field:int state; offset:24; size:4; signed:1;
field:__u16 sport; offset:28; size:2; signed:0;
field:__u16 dport; offset:30; size:2; signed:0;
field:__u16 family; offset:32; size:2; signed:0;
field:__u8 saddr[4]; offset:34; size:4; signed:0;
field:__u8 daddr[4]; offset:38; size:4; signed:0;
field:__u8 saddr_v6[16]; offset:42; size:16; signed:0;
field:__u8 daddr_v6[16]; offset:58; size:16; signed:0;
field:int err; offset:76; size:4; signed:1;
print fmt: "skbaddr=%p skaddr=%p family=%s sport=%hu dport=%hu saddr=%pI4 daddr=%pI4 saddrv6=%pI6c daddrv6=%pI6c state=%s err=%d"
Suggested-by: Jakub Kicinski <kuba@kernel.org>
Suggested-by: Eric Dumazet <edumazet@google.com>
Co-developed-by: xu xin <xu.xin16@zte.com.cn>
Signed-off-by: xu xin <xu.xin16@zte.com.cn>
Signed-off-by: Fan Yu <fan.yu9@zte.com.cn>
Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>
---
Change Log
=========
v6->v7:
Some fixes according to
https://lore.kernel.org/all/CAAVpQUCDJOnwRhjcwFke2vTZQ8rymopC3hpyPteLA3cRgXFz9Q@mail.gmail.com/#t
1. Fixed tags errors.
2. Add Reviewed-by tag.
v5->v6:
Some fixes according to
https://lore.kernel.org/all/20250715183335.860529-1-kuniyu@google.com/
1. Fixed HTML entity conversion in email and adjusted error counting logic.
v4->v5:
Some fixes according to
https://lore.kernel.org/all/20250715072058.12f343bb@kernel.org/
1. Instead of introducing new TCP_RETRANS_* enums, directly
passing the retval to the tracepoint.
v3->v4:
Some fixes according to
https://lore.kernel.org/all/CANn89i+JGSt=_CtWfhDXypWW-34a6SoP3RAzWQ9B9VL4+PHjDw@mail.gmail.com/
1. Consolidate ENOMEMs into a unified TCP_RETRANS_NOMEM.
v2->v3:
Some fixes according to
https://lore.kernel.org/all/CANn89iJvyYjiweCESQL8E-Si7M=gosYvh1BAVWwAWycXW8GSdg@mail.gmail.com/
1. Rename "quit_reason" to "result". Also, keep "key=val" format concise(no space in vals).
v1->v2:
Some fixes according to
https://lore.kernel.org/all/CANn89iK-6kT-ZUpNRMjPY9_TkQj-dLuKrDQtvO1140q4EUsjFg@mail.gmail.com/
1.Rename TCP_RETRANS_QUIT_UNDEFINED to TCP_RETRANS_ERR_DEFAULT.
2.Added detailed compatibility consequences section.
---
include/trace/events/tcp.h | 27 ++++++++--------------
net/ipv4/tcp_output.c | 46 ++++++++++++++++++++++++--------------
2 files changed, 38 insertions(+), 35 deletions(-)
diff --git a/include/trace/events/tcp.h b/include/trace/events/tcp.h
index 54e60c6009e3..9d2c36c6a0ed 100644
--- a/include/trace/events/tcp.h
+++ b/include/trace/events/tcp.h
@@ -13,17 +13,11 @@
#include <linux/sock_diag.h>
#include <net/rstreason.h>
-/*
- * tcp event with arguments sk and skb
- *
- * Note: this class requires a valid sk pointer; while skb pointer could
- * be NULL.
- */
-DECLARE_EVENT_CLASS(tcp_event_sk_skb,
+TRACE_EVENT(tcp_retransmit_skb,
- TP_PROTO(const struct sock *sk, const struct sk_buff *skb),
+ TP_PROTO(const struct sock *sk, const struct sk_buff *skb, int err),
- TP_ARGS(sk, skb),
+ TP_ARGS(sk, skb, err),
TP_STRUCT__entry(
__field(const void *, skbaddr)
@@ -36,6 +30,7 @@ DECLARE_EVENT_CLASS(tcp_event_sk_skb,
__array(__u8, daddr, 4)
__array(__u8, saddr_v6, 16)
__array(__u8, daddr_v6, 16)
+ __field(int, err)
),
TP_fast_assign(
@@ -58,21 +53,17 @@ DECLARE_EVENT_CLASS(tcp_event_sk_skb,
TP_STORE_ADDRS(__entry, inet->inet_saddr, inet->inet_daddr,
sk->sk_v6_rcv_saddr, sk->sk_v6_daddr);
+
+ __entry->err = err;
),
- TP_printk("skbaddr=%p skaddr=%p family=%s sport=%hu dport=%hu saddr=%pI4 daddr=%pI4 saddrv6=%pI6c daddrv6=%pI6c state=%s",
+ TP_printk("skbaddr=%p skaddr=%p family=%s sport=%hu dport=%hu saddr=%pI4 daddr=%pI4 saddrv6=%pI6c daddrv6=%pI6c state=%s err=%d",
__entry->skbaddr, __entry->skaddr,
show_family_name(__entry->family),
__entry->sport, __entry->dport, __entry->saddr, __entry->daddr,
__entry->saddr_v6, __entry->daddr_v6,
- show_tcp_state_name(__entry->state))
-);
-
-DEFINE_EVENT(tcp_event_sk_skb, tcp_retransmit_skb,
-
- TP_PROTO(const struct sock *sk, const struct sk_buff *skb),
-
- TP_ARGS(sk, skb)
+ show_tcp_state_name(__entry->state),
+ __entry->err)
);
#undef FN
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index b616776e3354..caf11920a878 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -3330,8 +3330,10 @@ int __tcp_retransmit_skb(struct sock *sk, struct sk_buff *skb, int segs)
if (icsk->icsk_mtup.probe_size)
icsk->icsk_mtup.probe_size = 0;
- if (skb_still_in_host_queue(sk, skb))
- return -EBUSY;
+ if (skb_still_in_host_queue(sk, skb)) {
+ err = -EBUSY;
+ goto out;
+ }
start:
if (before(TCP_SKB_CB(skb)->seq, tp->snd_una)) {
@@ -3342,14 +3344,19 @@ int __tcp_retransmit_skb(struct sock *sk, struct sk_buff *skb, int segs)
}
if (unlikely(before(TCP_SKB_CB(skb)->end_seq, tp->snd_una))) {
WARN_ON_ONCE(1);
- return -EINVAL;
+ err = -EINVAL;
+ goto out;
+ }
+ if (tcp_trim_head(sk, skb, tp->snd_una - TCP_SKB_CB(skb)->seq)) {
+ err = -ENOMEM;
+ goto out;
}
- if (tcp_trim_head(sk, skb, tp->snd_una - TCP_SKB_CB(skb)->seq))
- return -ENOMEM;
}
- if (inet_csk(sk)->icsk_af_ops->rebuild_header(sk))
- return -EHOSTUNREACH; /* Routing failure or similar. */
+ if (inet_csk(sk)->icsk_af_ops->rebuild_header(sk)) {
+ err = -EHOSTUNREACH; /* Routing failure or similar. */
+ goto out;
+ }
cur_mss = tcp_current_mss(sk);
avail_wnd = tcp_wnd_end(tp) - TCP_SKB_CB(skb)->seq;
@@ -3360,8 +3367,10 @@ int __tcp_retransmit_skb(struct sock *sk, struct sk_buff *skb, int segs)
* our retransmit of one segment serves as a zero window probe.
*/
if (avail_wnd <= 0) {
- if (TCP_SKB_CB(skb)->seq != tp->snd_una)
- return -EAGAIN;
+ if (TCP_SKB_CB(skb)->seq != tp->snd_una) {
+ err = -EAGAIN;
+ goto out;
+ }
avail_wnd = cur_mss;
}
@@ -3373,11 +3382,15 @@ int __tcp_retransmit_skb(struct sock *sk, struct sk_buff *skb, int segs)
}
if (skb->len > len) {
if (tcp_fragment(sk, TCP_FRAG_IN_RTX_QUEUE, skb, len,
- cur_mss, GFP_ATOMIC))
- return -ENOMEM; /* We'll try again later. */
+ cur_mss, GFP_ATOMIC)) {
+ err = -ENOMEM; /* We'll try again later. */
+ goto out;
+ }
} else {
- if (skb_unclone_keeptruesize(skb, GFP_ATOMIC))
- return -ENOMEM;
+ if (skb_unclone_keeptruesize(skb, GFP_ATOMIC)) {
+ err = -ENOMEM;
+ goto out;
+ }
diff = tcp_skb_pcount(skb);
tcp_set_skb_tso_segs(skb, cur_mss);
@@ -3431,17 +3444,16 @@ int __tcp_retransmit_skb(struct sock *sk, struct sk_buff *skb, int segs)
tcp_call_bpf_3arg(sk, BPF_SOCK_OPS_RETRANS_CB,
TCP_SKB_CB(skb)->seq, segs, err);
- if (likely(!err)) {
- trace_tcp_retransmit_skb(sk, skb);
- } else if (err != -EBUSY) {
+ if (unlikely(err) && err != -EBUSY)
NET_ADD_STATS(sock_net(sk), LINUX_MIB_TCPRETRANSFAIL, segs);
- }
/* To avoid taking spuriously low RTT samples based on a timestamp
* for a transmit that never happened, always mark EVER_RETRANS
*/
TCP_SKB_CB(skb)->sacked |= TCPCB_EVER_RETRANS;
+out:
+ trace_tcp_retransmit_skb(sk, skb, err);
return err;
}
--
2.25.1
^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
2025-07-21 3:16 [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb fan.yu9
@ 2025-07-22 0:13 ` Jakub Kicinski
2025-07-22 1:48 ` fan.yu9
2025-07-22 6:42 ` Eric Dumazet
2025-07-23 1:30 ` patchwork-bot+netdevbpf
2 siblings, 1 reply; 7+ messages in thread
From: Jakub Kicinski @ 2025-07-22 0:13 UTC (permalink / raw)
To: fan.yu9
Cc: edumazet, ncardwell, davem, dsahern, pabeni, horms, kuniyu,
rostedt, mhiramat, mathieu.desnoyers, netdev, linux-kernel,
linux-trace-kernel, yang.yang29, xu.xin16, tu.qiang35, jiang.kun2,
qiu.yutan, wang.yaxin, he.peilin
On Mon, 21 Jul 2025 11:16:07 +0800 (CST) fan.yu9@zte.com.cn wrote:
> Subject: [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
Why did you resend this??
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
2025-07-22 0:13 ` Jakub Kicinski
@ 2025-07-22 1:48 ` fan.yu9
2025-07-22 3:50 ` Kuniyuki Iwashima
0 siblings, 1 reply; 7+ messages in thread
From: fan.yu9 @ 2025-07-22 1:48 UTC (permalink / raw)
To: kuba
Cc: edumazet, ncardwell, davem, dsahern, pabeni, horms, kuniyu,
rostedt, mhiramat, mathieu.desnoyers, netdev, linux-kernel,
linux-trace-kernel, yang.yang29, xu.xin16, tu.qiang35, jiang.kun2,
qiu.yutan, wang.yaxin, he.peilin
[-- Attachment #1.1.1: Type: text/plain, Size: 417 bytes --]
> On Mon, 21 Jul 2025 11:16:07 +0800 (CST) fan.yu9@zte.com.cn wrote:
> > Subject: [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
>
> Why did you resend this??
Hi Jakub,
Thanks for checking! I just wanted to ensure the v7 patch wasn’t missed — it’s identical to the original.
Please let me know if any updates are needed. Appreciate your time!
Best regards,
Fan Yu
[-- Attachment #1.1.2: Type: text/html , Size: 542 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
2025-07-22 1:48 ` fan.yu9
@ 2025-07-22 3:50 ` Kuniyuki Iwashima
2025-07-22 6:10 ` fan.yu9
0 siblings, 1 reply; 7+ messages in thread
From: Kuniyuki Iwashima @ 2025-07-22 3:50 UTC (permalink / raw)
To: fan.yu9
Cc: kuba, edumazet, ncardwell, davem, dsahern, pabeni, horms, rostedt,
mhiramat, mathieu.desnoyers, netdev, linux-kernel,
linux-trace-kernel, yang.yang29, xu.xin16, tu.qiang35, jiang.kun2,
qiu.yutan, wang.yaxin, he.peilin
On Mon, Jul 21, 2025 at 6:48 PM <fan.yu9@zte.com.cn> wrote:
>
> > On Mon, 21 Jul 2025 11:16:07 +0800 (CST) fan.yu9@zte.com.cn wrote:
>
> > > Subject: [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
>
> >
>
> > Why did you resend this??
>
>
> Hi Jakub,
>
>
> Thanks for checking! I just wanted to ensure the v7 patch wasn’t missed — it’s identical to the original.
You can check the patch status in patchwork, and actually this v7
marked the previous v7 as Superseded, so you didn't need to resend :)
https://patchwork.kernel.org/project/netdevbpf/list/?submitter=217549&state=*
>
> Please let me know if any updates are needed. Appreciate your time!
>
>
> Best regards,
>
> Fan Yu
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
2025-07-22 3:50 ` Kuniyuki Iwashima
@ 2025-07-22 6:10 ` fan.yu9
0 siblings, 0 replies; 7+ messages in thread
From: fan.yu9 @ 2025-07-22 6:10 UTC (permalink / raw)
To: kuniyu
Cc: kuba, edumazet, ncardwell, davem, dsahern, pabeni, horms, rostedt,
mhiramat, mathieu.desnoyers, netdev, linux-kernel,
linux-trace-kernel, yang.yang29, xu.xin16, tu.qiang35, jiang.kun2,
qiu.yutan, wang.yaxin, he.peilin
[-- Attachment #1.1.1: Type: text/plain, Size: 607 bytes --]
> > Thanks for checking! I just wanted to ensure the v7 patch wasn’t missed — it’s identical to the original.
>
> You can check the patch status in patchwork, and actually this v7
> marked the previous v7 as Superseded, so you didn't need to resend :)
>
> https://patchwork.kernel.org/project/netdevbpf/list/?submitter=217549&state=*
Hi Kuniyuki,
Thanks for the clarification! I’ve checked the Patchwork link and now
see the v7 status("New"). My apologies for the redundant resend — I’ll
avoid this in the future.
Appreciate your patience and guidance!
Best regards,
Fan Yu
[-- Attachment #1.1.2: Type: text/html , Size: 776 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
2025-07-21 3:16 [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb fan.yu9
2025-07-22 0:13 ` Jakub Kicinski
@ 2025-07-22 6:42 ` Eric Dumazet
2025-07-23 1:30 ` patchwork-bot+netdevbpf
2 siblings, 0 replies; 7+ messages in thread
From: Eric Dumazet @ 2025-07-22 6:42 UTC (permalink / raw)
To: fan.yu9
Cc: kuba, ncardwell, davem, dsahern, pabeni, horms, kuniyu, rostedt,
mhiramat, mathieu.desnoyers, netdev, linux-kernel,
linux-trace-kernel, yang.yang29, xu.xin16, tu.qiang35, jiang.kun2,
qiu.yutan, wang.yaxin, he.peilin
On Sun, Jul 20, 2025 at 8:16 PM <fan.yu9@zte.com.cn> wrote:
>
> From: Fan Yu <fan.yu9@zte.com.cn>
>
> Background
> ==========
> When TCP retransmits a packet due to missing ACKs, the
> retransmission may fail for various reasons (e.g., packets
> stuck in driver queues, receiver zero windows, or routing issues).
>
> The original tcp_retransmit_skb tracepoint:
>
> 'commit e086101b150a ("tcp: add a tracepoint for tcp retransmission")'
>
> lacks visibility into these failure causes, making production
> diagnostics difficult.
>
>
> Suggested-by: Jakub Kicinski <kuba@kernel.org>
> Suggested-by: Eric Dumazet <edumazet@google.com>
> Co-developed-by: xu xin <xu.xin16@zte.com.cn>
> Signed-off-by: xu xin <xu.xin16@zte.com.cn>
> Signed-off-by: Fan Yu <fan.yu9@zte.com.cn>
> Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>
Please do not add a Suggested-by tag when the original idea did not
come from someone else.
I only made suggestions to make your patch better.
Reviewed-by: Eric Dumazet <edumazet@google.com>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
2025-07-21 3:16 [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb fan.yu9
2025-07-22 0:13 ` Jakub Kicinski
2025-07-22 6:42 ` Eric Dumazet
@ 2025-07-23 1:30 ` patchwork-bot+netdevbpf
2 siblings, 0 replies; 7+ messages in thread
From: patchwork-bot+netdevbpf @ 2025-07-23 1:30 UTC (permalink / raw)
To: fan.yu9
Cc: kuba, edumazet, ncardwell, davem, dsahern, pabeni, horms, kuniyu,
rostedt, mhiramat, mathieu.desnoyers, netdev, linux-kernel,
linux-trace-kernel, yang.yang29, xu.xin16, tu.qiang35, jiang.kun2,
qiu.yutan, wang.yaxin, he.peilin
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Jul 2025 11:16:07 +0800 (CST) you wrote:
> From: Fan Yu <fan.yu9@zte.com.cn>
>
> Background
> ==========
> When TCP retransmits a packet due to missing ACKs, the
> retransmission may fail for various reasons (e.g., packets
> stuck in driver queues, receiver zero windows, or routing issues).
>
> [...]
Here is the summary with links:
- [net-next,v7,RESEND] tcp: trace retransmit failures in tcp_retransmit_skb
https://git.kernel.org/netdev/net-next/c/ad892e912b84
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2025-07-23 1:30 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-07-21 3:16 [PATCH net-next v7 RESEND] tcp: trace retransmit failures in tcp_retransmit_skb fan.yu9
2025-07-22 0:13 ` Jakub Kicinski
2025-07-22 1:48 ` fan.yu9
2025-07-22 3:50 ` Kuniyuki Iwashima
2025-07-22 6:10 ` fan.yu9
2025-07-22 6:42 ` Eric Dumazet
2025-07-23 1:30 ` patchwork-bot+netdevbpf
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).