From: patchwork-bot+netdevbpf@kernel.org
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: edumazet@google.com, dsahern@kernel.org, matttbe@kernel.org,
martineau@kernel.org, geliang@kernel.org, kuba@kernel.org,
pabeni@redhat.com, davem@davemloft.net, rostedt@goodmis.org,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
atenart@kernel.org, horms@kernel.org, mptcp@lists.linux.dev,
netdev@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
kernelxing@tencent.com
Subject: Re: [PATCH net-next v9 0/7] Implement reset reason mechanism to detect
Date: Fri, 26 Apr 2024 13:40:29 +0000 [thread overview]
Message-ID: <171413882983.4140.2846723996331874537.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240425031340.46946-1-kerneljasonxing@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 25 Apr 2024 11:13:33 +0800 you wrote:
> From: Jason Xing <kernelxing@tencent.com>
>
> In production, there are so many cases about why the RST skb is sent but
> we don't have a very convenient/fast method to detect the exact underlying
> reasons.
>
> RST is implemented in two kinds: passive kind (like tcp_v4_send_reset())
> and active kind (like tcp_send_active_reset()). The former can be traced
> carefully 1) in TCP, with the help of drop reasons, which is based on
> Eric's idea[1], 2) in MPTCP, with the help of reset options defined in
> RFC 8684. The latter is relatively independent, which should be
> implemented on our own, such as active reset reasons which can not be
> replace by skb drop reason or something like this.
>
> [...]
Here is the summary with links:
- [net-next,v9,1/7] net: introduce rstreason to detect why the RST is sent
https://git.kernel.org/netdev/net-next/c/5cb2cb3cb20c
- [net-next,v9,2/7] rstreason: prepare for passive reset
https://git.kernel.org/netdev/net-next/c/6be49deaa095
- [net-next,v9,3/7] rstreason: prepare for active reset
https://git.kernel.org/netdev/net-next/c/5691276b39da
- [net-next,v9,4/7] tcp: support rstreason for passive reset
https://git.kernel.org/netdev/net-next/c/120391ef9ca8
- [net-next,v9,5/7] mptcp: support rstreason for passive reset
https://git.kernel.org/netdev/net-next/c/3e140491dd80
- [net-next,v9,6/7] mptcp: introducing a helper into active reset logic
https://git.kernel.org/netdev/net-next/c/215d40248bde
- [net-next,v9,7/7] rstreason: make it work in trace world
https://git.kernel.org/netdev/net-next/c/b533fb9cf4f7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-04-26 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 3:13 [PATCH net-next v9 0/7] Implement reset reason mechanism to detect Jason Xing
2024-04-25 3:13 ` [PATCH net-next v9 1/7] net: introduce rstreason to detect why the RST is sent Jason Xing
2024-04-26 7:09 ` Eric Dumazet
2024-04-25 3:13 ` [PATCH net-next v9 2/7] rstreason: prepare for passive reset Jason Xing
2024-04-26 7:10 ` Eric Dumazet
2024-04-25 3:13 ` [PATCH net-next v9 3/7] rstreason: prepare for active reset Jason Xing
2024-04-26 7:10 ` Eric Dumazet
2024-04-25 3:13 ` [PATCH net-next v9 4/7] tcp: support rstreason for passive reset Jason Xing
2024-04-25 3:13 ` [PATCH net-next v9 5/7] mptcp: " Jason Xing
2024-04-26 7:11 ` Eric Dumazet
2024-04-25 3:13 ` [PATCH net-next v9 6/7] mptcp: introducing a helper into active reset logic Jason Xing
2024-04-26 7:11 ` Eric Dumazet
2024-04-25 3:13 ` [PATCH net-next v9 7/7] rstreason: make it work in trace world Jason Xing
2024-04-26 7:12 ` Eric Dumazet
2024-04-26 7:12 ` [PATCH net-next v9 0/7] Implement reset reason mechanism to detect Eric Dumazet
2024-04-26 13:40 ` patchwork-bot+netdevbpf [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=171413882983.4140.2846723996331874537.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=matttbe@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mptcp@lists.linux.dev \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).