netdev - Re: [PATCH v2] tcp: relookup sock for RST+ACK packets handled by obsolete req sock

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:   Mon, 15 Mar 2021 21:50:07 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Alexander Ovechkin <ovov@...dex-team.ru>
Cc:     netdev@...r.kernel.org, edumazet@...gle.com, davem@...emloft.net,
        zeil@...dex-team.ru, dmtrmonakhov@...dex-team.ru,
        olegsenin@...dex-team.ru
Subject: Re: [PATCH v2] tcp: relookup sock for RST+ACK packets handled by obsolete
 req sock

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Mon, 15 Mar 2021 14:05:45 +0300 you wrote:
> Currently tcp_check_req can be called with obsolete req socket for which big
> socket have been already created (because of CPU race or early demux
> assigning req socket to multiple packets in gro batch).
> 
> Commit e0f9759f530bf789e984 ("tcp: try to keep packet if SYN_RCV race
> is lost") added retry in case when tcp_check_req is called for PSH|ACK packet.
> But if client sends RST+ACK immediatly after connection being
> established (it is performing healthcheck, for example) retry does not
> occur. In that case tcp_check_req tries to close req socket,
> leaving big socket active.
> 
> [...]

Here is the summary with links:
  - [v2] tcp: relookup sock for RST+ACK packets handled by obsolete req sock
    https://git.kernel.org/netdev/net/c/7233da86697e

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