From: Jason Xing <kerneljasonxing@gmail.com>
To: edumazet@google.com, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, rostedt@goodmis.org,
kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
kerneljasonxing@gmail.com, Jason Xing <kernelxing@tencent.com>
Subject: [PATCH net-next v4 0/2] tcp: make trace of reset logic complete
Date: Mon, 1 Apr 2024 15:36:03 +0800 [thread overview]
Message-ID: <20240401073605.37335-1-kerneljasonxing@gmail.com> (raw)
From: Jason Xing <kernelxing@tencent.com>
Before this, we miss some cases where the TCP layer could send RST but
we cannot trace it. So I decided to complete it :)
v4
Link: https://lore.kernel.org/all/20240329034243.7929-1-kerneljasonxing@gmail.com/
1. rebased against latest net-next
2. remove {} and add skb test statement (Eric)
3. drop v3 patch [3/3] temporarily because 1) location is not that useful
since we can use perf or something else to trace, 2) Eric said we could
use drop_reason to show why we have to RST, which is good, but this seems
not work well for those ->send_reset() logic. I need more time to
investigate this part.
v3
1. fix a format problem in patch [3/3]
v2
1. fix spelling mistakes
Jason Xing (2):
trace: adjust TP_STORE_ADDR_PORTS_SKB() parameters
trace: tcp: fully support trace_tcp_send_reset
include/trace/events/net_probe_common.h | 20 ++++++------
include/trace/events/tcp.h | 42 +++++++++++++++++++++++--
include/trace/events/udp.h | 2 +-
net/ipv4/tcp_ipv4.c | 7 ++---
net/ipv6/tcp_ipv6.c | 3 +-
5 files changed, 56 insertions(+), 18 deletions(-)
--
2.37.3
next reply other threads:[~2024-04-01 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 7:36 Jason Xing [this message]
2024-04-01 7:36 ` [PATCH net-next v4 1/2] trace: adjust TP_STORE_ADDR_PORTS_SKB() parameters Jason Xing
2024-04-01 7:36 ` [PATCH net-next v4 2/2] trace: tcp: fully support trace_tcp_send_reset Jason Xing
2024-04-04 2:30 ` [PATCH net-next v4 0/2] tcp: make trace of reset logic complete patchwork-bot+netdevbpf
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=20240401073605.37335-1-kerneljasonxing@gmail.com \
--to=kerneljasonxing@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.