[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174433803599.3928161.6673282068202917345.git-patchwork-notify@kernel.org>
Date: Fri, 11 Apr 2025 02:20:35 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jiayuan Chen <jiayuan.chen@...ux.dev>
Cc: kuba@...nel.org, edumazet@...gle.com, mrpre@....com, davem@...emloft.net,
pabeni@...hat.com, horms@...nel.org, corbet@....net, ncardwell@...gle.com,
kuniyu@...zon.com, dsahern@...nel.org, steffen.klassert@...unet.com,
sd@...asysnail.net, antony.antony@...unet.com, chopps@...n.net,
netdev@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v4 0/2] tcp: add a new TW_PAWS drop reason
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 9 Apr 2025 19:26:03 +0800 you wrote:
> Devices in the networking path, such as firewalls, NATs, or routers, which
> can perform SNAT or DNAT, use addresses from their own limited address
> pools to masquerade the source address during forwarding, causing PAWS
> verification to fail more easily under TW status.
>
> Currently, packet loss statistics for PAWS can only be viewed through MIB,
> which is a global metric and cannot be precisely obtained through tracing
> to get the specific 4-tuple of the dropped packet. In the past, we had to
> use kprobe ret to retrieve relevant skb information from
> tcp_timewait_state_process().
>
> [...]
Here is the summary with links:
- [net-next,v4,1/2] tcp: add TCP_RFC7323_TW_PAWS drop reason
https://git.kernel.org/netdev/net-next/c/04271411121a
- [net-next,v4,2/2] tcp: add LINUX_MIB_PAWS_TW_REJECTED counter
https://git.kernel.org/netdev/net-next/c/c449d5f3a3d7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists