| 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
| ||
|
Message-Id:
<172470662501.127664.3509173405619700960.git-patchwork-notify@kernel.org>
Date: Mon, 26 Aug 2024 21:10:25 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jason Xing <kerneljasonxing@...il.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, dsahern@...nel.org, kuniyu@...zon.com,
netdev@...r.kernel.org, kernelxing@...cent.com, jadedong@...cent.com
Subject: Re: [PATCH v4 net-next] tcp: avoid reusing FIN_WAIT2 when trying to find
port in connect() process
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Fri, 23 Aug 2024 08:11:52 +0800 you wrote:
> From: Jason Xing <kernelxing@...cent.com>
>
> We found that one close-wait socket was reset by the other side
> due to a new connection reusing the same port which is beyond our
> expectation, so we have to investigate the underlying reason.
>
> The following experiment is conducted in the test environment. We
> limit the port range from 40000 to 40010 and delay the time to close()
> after receiving a fin from the active close side, which can help us
> easily reproduce like what happened in production.
>
> [...]
Here is the summary with links:
- [v4,net-next] tcp: avoid reusing FIN_WAIT2 when trying to find port in connect() process
https://git.kernel.org/netdev/net-next/c/0d9e5df4a257
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