From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cc: martineau@kernel.org, geliang@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, donald.hunter@gmail.com, fw@strlen.de,
kishen.maloor@intel.com, shuah@kernel.org, dmytro@shytyi.net,
netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
marek@cloudflare.com
Subject: Re: [PATCH net 0/5] mptcp: pm: nl: announce deny-join-id0 flag
Date: Tue, 16 Sep 2025 01:30:18 +0000 [thread overview]
Message-ID: <175798621825.559370.16652026022818101575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250912-net-mptcp-pm-uspace-deny_join_id0-v1-0-40171884ade8@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 12 Sep 2025 14:52:19 +0200 you wrote:
> During the connection establishment, a peer can tell the other one that
> it cannot establish new subflows to the initial IP address and port by
> setting the 'C' flag [1]. Doing so makes sense when the sender is behind
> a strict NAT, operating behind a legacy Layer 4 load balancer, or using
> anycast IP address for example.
>
> When this 'C' flag is set, the path-managers must then not try to
> establish new subflows to the other peer's initial IP address and port.
> The in-kernel PM has access to this info, but the userspace PM didn't,
> not letting the userspace daemon able to respect the RFC8684.
>
> [...]
Here is the summary with links:
- [net,1/5] mptcp: set remote_deny_join_id0 on SYN recv
https://git.kernel.org/netdev/net/c/96939cec9940
- [net,2/5] mptcp: pm: nl: announce deny-join-id0 flag
https://git.kernel.org/netdev/net/c/2293c57484ae
- [net,3/5] selftests: mptcp: userspace pm: validate deny-join-id0 flag
https://git.kernel.org/netdev/net/c/24733e193a0d
- [net,4/5] mptcp: tfo: record 'deny join id0' info
https://git.kernel.org/netdev/net/c/92da495cb657
- [net,5/5] selftests: mptcp: sockopt: fix error messages
https://git.kernel.org/netdev/net/c/b86418beade1
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:[~2025-09-16 1:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 12:52 [PATCH net 0/5] mptcp: pm: nl: announce deny-join-id0 flag Matthieu Baerts (NGI0)
2025-09-12 12:52 ` [PATCH net 1/5] mptcp: set remote_deny_join_id0 on SYN recv Matthieu Baerts (NGI0)
2025-09-12 12:52 ` [PATCH net 2/5] mptcp: pm: nl: announce deny-join-id0 flag Matthieu Baerts (NGI0)
2025-09-12 12:52 ` [PATCH net 3/5] selftests: mptcp: userspace pm: validate " Matthieu Baerts (NGI0)
2025-09-12 12:52 ` [PATCH net 4/5] mptcp: tfo: record 'deny join id0' info Matthieu Baerts (NGI0)
2025-09-12 12:52 ` [PATCH net 5/5] selftests: mptcp: sockopt: fix error messages Matthieu Baerts (NGI0)
2025-09-16 1:30 ` 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=175798621825.559370.16652026022818101575.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dmytro@shytyi.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kishen.maloor@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=marek@cloudflare.com \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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