From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <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, netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-kernel@vger.kernel.org, corbet@lwn.net,
skhan@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org, ncardwell@google.com,
kuniyu@google.com, shuah@kernel.org
Subject: Re: [PATCH net-next v2 00/15] mptcp: pm: drop TCP TS with ADD_ADDRv6 + port
Date: Thu, 11 Jun 2026 22:50:28 +0000 [thread overview]
Message-ID: <178121822814.394849.2368301778556817000.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260605-net-next-mptcp-add-addr6-port-ts-v2-0-758e7ca73f4d@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 05 Jun 2026 19:21:44 +1000 you wrote:
> Up to this series, it was possible to add a "signal" MPTCP endpoint with
> an IPv6 address and a port, or to directly request to send an ADD_ADDR
> with a v6 address and a port, but the expected ADD_ADDR wasn't sent when
> TCP timestamps was used for the connection.
>
> In fact, such signalling option cannot be sent when TCP timestamps is
> used due to a lack of option space: the limit is at 40 bytes, and, with
> padding, TCP timestamps is taking 12 bytes, while an ADD_ADDR IPv6 +
> port is taking 30 bytes. The selected solution here is to simply drop
> the TCP timestamps option when such ADD_ADDR of 30 bytes needs to be
> sent.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/15] mptcp: options: suboptions sizes can be negative
https://git.kernel.org/netdev/net-next/c/f4a58ffbd4cf
- [net-next,v2,02/15] mptcp: pm: avoid computing rm_addr size twice
https://git.kernel.org/netdev/net-next/c/a8bffec089d5
- [net-next,v2,03/15] mptcp: pm: avoid computing add_addr size twice
https://git.kernel.org/netdev/net-next/c/06c62385be85
- [net-next,v2,04/15] mptcp: introduce add_addr_v6_port_drop_ts sysctl knob
https://git.kernel.org/netdev/net-next/c/30ff28fdc4da
- [net-next,v2,05/15] tcp: allow mptcp to drop TS for some packets
https://git.kernel.org/netdev/net-next/c/1c3e7e043977
- [net-next,v2,06/15] mptcp: pm: drop TCP TS with ADD_ADDRv6 + port
https://git.kernel.org/netdev/net-next/c/23eeaad0d89d
- [net-next,v2,07/15] selftests: mptcp: validate ADD_ADDRv6 + TS + port
https://git.kernel.org/netdev/net-next/c/dd7fb53c21c3
- [net-next,v2,08/15] selftests: mptcp: always check sent/dropped ADD_ADDRs
https://git.kernel.org/netdev/net-next/c/5558517b0001
- [net-next,v2,09/15] mptcp: pm: use for_each_subflow helper
https://git.kernel.org/netdev/net-next/c/f81689172429
- [net-next,v2,10/15] mptcp: pm: rename add_entry structure to add_addr
https://git.kernel.org/netdev/net-next/c/350d76dd6e79
- [net-next,v2,11/15] mptcp: pm: uniform announced addresses helpers
https://git.kernel.org/netdev/net-next/c/7d4dacc8ccca
- [net-next,v2,12/15] mptcp: pm: remove add_ prefix from timer
https://git.kernel.org/netdev/net-next/c/938490767e37
- [net-next,v2,13/15] mptcp: pm: make mptcp_pm_add_addr_send_ack static
https://git.kernel.org/netdev/net-next/c/d0f866e64897
- [net-next,v2,14/15] mptcp: pm: avoid using del_timer directly
https://git.kernel.org/netdev/net-next/c/6ea199a938da
- [net-next,v2,15/15] mptcp: options: rst: drop unused skb parameter
https://git.kernel.org/netdev/net-next/c/6545a8c34703
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-06-11 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 9:21 [PATCH net-next v2 00/15] mptcp: pm: drop TCP TS with ADD_ADDRv6 + port Matthieu Baerts (NGI0)
2026-06-05 9:21 ` [PATCH net-next v2 04/15] mptcp: introduce add_addr_v6_port_drop_ts sysctl knob Matthieu Baerts (NGI0)
2026-06-11 22: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=178121822814.394849.2368301778556817000.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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