From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Brivio <sbrivio@redhat.com>
Cc: willemdebruijn.kernel@gmail.com, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org, kuniyu@amazon.com,
mvrmanning@gmail.com, david@gibson.dropbear.id.au,
pholzing@redhat.com, lulie@linux.alibaba.com,
cambda@linux.alibaba.com, fred.cc@alibaba-inc.com,
yubing.qiuyubing@alibaba-inc.com, posk@google.com
Subject: Re: [PATCH net-next v2] udp: Deal with race between UDP socket address change and rehash
Date: Mon, 23 Dec 2024 11:50:29 +0000 [thread overview]
Message-ID: <173495462976.3848117.16494580835823319856.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241218162116.681734-1-sbrivio@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.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
prev parent reply other threads:[~2024-12-23 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 16:21 [PATCH net-next v2] udp: Deal with race between UDP socket address change and rehash Stefano Brivio
2024-12-20 14:16 ` Eric Dumazet
2024-12-20 15:05 ` Stefano Brivio
2024-12-21 15:24 ` Willem de Bruijn
2024-12-23 11:50 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=173495462976.3848117.16494580835823319856.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cambda@linux.alibaba.com \
--cc=david@gibson.dropbear.id.au \
--cc=edumazet@google.com \
--cc=fred.cc@alibaba-inc.com \
--cc=kuniyu@amazon.com \
--cc=lulie@linux.alibaba.com \
--cc=mvrmanning@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pholzing@redhat.com \
--cc=posk@google.com \
--cc=sbrivio@redhat.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yubing.qiuyubing@alibaba-inc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox