From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, stable+noautosel@kernel.org,
willemdebruijn.kernel@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, shuah@kernel.org, therbert@google.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] udp: fix auto-selected port colliding with an existing SO_REUSEPORT socket
Date: Wed, 30 Sep 2026 00:00:05 +0000 [thread overview]
Message-ID: <179072640545.1172483.6005581645683359247.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260928023145.301855-1-jiayuan.chen@linux.dev>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 28 Sep 2026 10:31:41 +0800 you wrote:
> Observed with two independent servers in the same process:
>
> fd1 = socket(AF_INET, SOCK_DGRAM, 0);
> setsockopt(fd1, SOL_SOCKET, SO_REUSEPORT, ...);
> bind(fd1, port 0); /* got 40000 */
>
> fd2 = socket(AF_INET, SOCK_DGRAM, 0);
> setsockopt(fd2, SOL_SOCKET, SO_REUSEPORT, ...);
> bind(fd2, port 0); /* got 40000 as well */
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] udp: fix auto-selected port colliding with an existing SO_REUSEPORT socket
https://git.kernel.org/netdev/net-next/c/20d020a07536
- [net-next,v2,2/2] selftests/net: check auto-selected port with reuse options
https://git.kernel.org/netdev/net-next/c/883c308be425
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:[~2026-09-30 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 2:31 [PATCH net-next v2 1/2] udp: fix auto-selected port colliding with an existing SO_REUSEPORT socket Jiayuan Chen
2026-09-28 2:31 ` [PATCH net-next v2 2/2] selftests/net: check auto-selected port with reuse options Jiayuan Chen
2026-09-30 0:00 ` 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=179072640545.1172483.6005581645683359247.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=stable+noautosel@kernel.org \
--cc=therbert@google.com \
--cc=willemdebruijn.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.