From: patchwork-bot+netdevbpf@kernel.org
To: Zhenzhong Wu <jt26wzz@gmail.com>
Cc: netdev@vger.kernel.org, edumazet@google.com,
ncardwell@google.com, kuniyu@google.com, davem@davemloft.net,
dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, shuah@kernel.org, tamird@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v4 0/2] tcp: fix listener wakeup after reuseport migration
Date: Thu, 23 Apr 2026 19:10:23 +0000 [thread overview]
Message-ID: <177697142304.724716.2732259563165568513.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260422024554.130346-1-jt26wzz@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 22 Apr 2026 10:45:52 +0800 you wrote:
> This series fixes a missing wakeup when inet_csk_listen_stop() migrates
> an established child socket from a closing listener to another socket
> in the same SO_REUSEPORT group after the child has already been queued
> for accept.
>
> The target listener receives the migrated accept-queue entry via
> inet_csk_reqsk_queue_add(), but its waiters are not notified.
> Nonblocking accept() still succeeds because it checks the accept queue
> directly, but readiness-based waiters can remain asleep until another
> connection generates a wakeup.
>
> [...]
Here is the summary with links:
- [net,v4,1/2] tcp: call sk_data_ready() after listener migration
https://git.kernel.org/netdev/net/c/3864c6ba1e04
- [net,v4,2/2] selftests/bpf: check epoll readiness during reuseport migration
https://git.kernel.org/netdev/net/c/c01cfc488675
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-04-23 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 2:45 [PATCH net v4 0/2] tcp: fix listener wakeup after reuseport migration Zhenzhong Wu
2026-04-22 2:45 ` [PATCH net v4 1/2] tcp: call sk_data_ready() after listener migration Zhenzhong Wu
2026-04-22 15:56 ` Eric Dumazet
2026-04-22 2:45 ` [PATCH net v4 2/2] selftests/bpf: check epoll readiness during reuseport migration Zhenzhong Wu
2026-04-22 3:03 ` Tamir Duberstein
2026-04-22 6:34 ` Zhenzhong Wu
2026-04-22 6:40 ` Kuniyuki Iwashima
2026-04-22 7:14 ` Zhenzhong Wu
2026-04-23 19:10 ` 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=177697142304.724716.2732259563165568513.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jt26wzz@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=tamird@kernel.org \
/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