From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
matttbe@kernel.org, martineau@kernel.org, geliang@kernel.org,
horms@kernel.org, kuniyu@google.com, netdev@vger.kernel.org,
kylebot@openai.com, stable@vger.kernel.org
Subject: Re: [PATCH net] mptcp: pm: kernel: use RCU to free endpoint listeners
Date: Thu, 05 Nov 2026 14:10:07 +0000 [thread overview]
Message-ID: <179388780704.3729553.7318793746811801977.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104125327.1041456-1-edumazet@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 4 Nov 2026 13:53:27 +0100 you wrote:
> From: Kyle Zeng <kylebot@openai.com>
>
> mptcp_pm_nl_create_listen_socket() starts the TCP listener directly
> instead of going through mptcp_listen(). It consequently misses setting
> SOCK_RCU_FREE on the parent MPTCP socket.
>
> tcp_child_process() can invoke the listener's subflow_data_ready()
> callback without holding the MPTCP parent lock or a reference to the
> parent. An authenticated MP_JOIN racing with endpoint teardown can
> therefore access the parent after its last reference has been dropped.
> The ADD_ADDR error path can also close an already published listener.
>
> [...]
Here is the summary with links:
- [net] mptcp: pm: kernel: use RCU to free endpoint listeners
https://git.kernel.org/netdev/net/c/49b09ae0bf57
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-11-05 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 12:53 [PATCH net] mptcp: pm: kernel: use RCU to free endpoint listeners Eric Dumazet
2026-11-04 12:59 ` netdev-bot+sinfo
2026-11-04 15:37 ` Matthieu Baerts
2026-11-05 14: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=179388780704.3729553.7318793746811801977.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=kylebot@openai.com \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.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