netdev - Re: [PATCH net-next] ipv6: tcp: send consistent autoflowlabel in SYN

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: <166209181498.19149.13471751013086116719.git-patchwork-notify@kernel.org>
Date:   Fri, 02 Sep 2022 04:10:14 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Eric Dumazet <eric.dumazet@...il.com>
Cc:     davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
        netdev@...r.kernel.org, ncardwell@...gle.com, edumazet@...gle.com
Subject: Re: [PATCH net-next] ipv6: tcp: send consistent autoflowlabel in SYN_RECV
 state

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.org>:

On Wed, 31 Aug 2022 13:37:29 -0700 you wrote:
> From: Eric Dumazet <edumazet@...gle.com>
> 
> This is a followup of commit c67b85558ff2 ("ipv6: tcp: send consistent
> autoflowlabel in TIME_WAIT state"), but for SYN_RECV state.
> 
> In some cases, TCP sends a challenge ACK on behalf of a SYN_RECV request.
> WHen this happens, we want to use the flow label that was used when
> the prior SYNACK packet was sent, instead of another one.
> 
> [...]

Here is the summary with links:
  - [net-next] ipv6: tcp: send consistent autoflowlabel in SYN_RECV state
    https://git.kernel.org/netdev/net-next/c/aa51b80e1af4

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