[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173495462976.3848117.16494580835823319856.git-patchwork-notify@kernel.org>
Date: Mon, 23 Dec 2024 11:50:29 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Stefano Brivio <sbrivio@...hat.com>
Cc: willemdebruijn.kernel@...il.com, pabeni@...hat.com, edumazet@...gle.com,
netdev@...r.kernel.org, kuniyu@...zon.com, mvrmanning@...il.com,
david@...son.dropbear.id.au, pholzing@...hat.com, lulie@...ux.alibaba.com,
cambda@...ux.alibaba.com, fred.cc@...baba-inc.com,
yubing.qiuyubing@...baba-inc.com, posk@...gle.com
Subject: Re: [PATCH net-next v2] udp: Deal with race between UDP socket address
change and rehash
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:
On Wed, 18 Dec 2024 17:21:16 +0100 you wrote:
> If a UDP socket changes its local address while it's receiving
> datagrams, as a result of connect(), there is a period during which
> a lookup operation might fail to find it, after the address is changed
> but before the secondary hash (port and address) and the four-tuple
> hash (local and remote ports and addresses) are updated.
>
> Secondary hash chains were introduced by commit 30fff9231fad ("udp:
> bind() optimisation") and, as a result, a rehash operation became
> needed to make a bound socket reachable again after a connect().
>
> [...]
Here is the summary with links:
- [net-next,v2] udp: Deal with race between UDP socket address change and rehash
https://git.kernel.org/netdev/net-next/c/a502ea6fa94b
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