netdev - Re: [PATCH net-next v9 0/7] Implement reset reason mechanism to detect

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Fri, 26 Apr 2024 13:40:29 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jason Xing <kerneljasonxing@...il.com>
Cc: edumazet@...gle.com, dsahern@...nel.org, matttbe@...nel.org,
 martineau@...nel.org, geliang@...nel.org, kuba@...nel.org, pabeni@...hat.com,
 davem@...emloft.net, rostedt@...dmis.org, mhiramat@...nel.org,
 mathieu.desnoyers@...icios.com, atenart@...nel.org, horms@...nel.org,
 mptcp@...ts.linux.dev, netdev@...r.kernel.org,
 linux-trace-kernel@...r.kernel.org, kernelxing@...cent.com
Subject: Re: [PATCH net-next v9 0/7] Implement reset reason mechanism to detect

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@...hat.com>:

On Thu, 25 Apr 2024 11:13:33 +0800 you wrote:
> From: Jason Xing <kernelxing@...cent.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