netdev - Re: [PATCH v3 net-next] tcp: Refine SYN handling for PAWS.

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]

Message-Id: <168025081746.23963.3556017879967087708.git-patchwork-notify@kernel.org>
Date:   Fri, 31 Mar 2023 08:20:17 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Kuniyuki Iwashima <kuniyu@...zon.com>
Cc:     davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
        pabeni@...hat.com, kuni1840@...il.com, netdev@...r.kernel.org,
        kerneljasonxing@...il.com
Subject: Re: [PATCH v3 net-next] tcp: Refine SYN handling for PAWS.

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:

On Wed, 29 Mar 2023 13:13:48 -0700 you wrote:
> Our Network Load Balancer (NLB) [0] has multiple nodes with different
> IP addresses, and each node forwards TCP flows from clients to backend
> targets.  NLB has an option to preserve the client's source IP address
> and port when routing packets to backend targets. [1]
> 
> When a client connects to two different NLB nodes, they may select the
> same backend target.  Then, if the client has used the same source IP
> and port, the two flows at the backend side will have the same 4-tuple.
> 
> [...]

Here is the summary with links:
  - [v3,net-next] tcp: Refine SYN handling for PAWS.
    https://git.kernel.org/netdev/net-next/c/ee05d90d0ac7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html