Re: [PATCH mptcp-net v2 0/2] mptcp: pm: in-kernel: usable client side with C-flag

[Matthieu Baerts <matttbe@kernel.org>]

On 19/09/2025 12:47, Matthieu Baerts wrote:
> Hi Geliang,
> 
> On 19/09/2025 12:15, Geliang Tang wrote:
>> Hi Matt,
>>
>> On Tue, 2025-09-16 at 13:01 +0200, Matthieu Baerts (NGI0) wrote:
>>> When servers set the C-flag in their MP_CAPABLE to tell clients not
>>> to
>>> create subflows to the initial address and port, clients will likely
>>> not
>>> use their other endpoints. That's because the in-kernel path-manager
>>> uses the 'subflow' endpoints to create subflows only to the initial
>>> address and port.
>>>
>>> The first patch fixes that, and the second one validates it.
>>>
>>> More details:
>>> https://github.com/multipath-tcp/mptcp_net-next/issues/536
>>>
>>> Please see the comment in the first patch, and don't hesitate to
>>> reply :)
>>>
>>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>>
>> Thanks for this v2.
>>
>> LGTM!
>>
>> Reviewed-by: Geliang Tang <geliang@kernel.org>
> 
> Thank you for the review!
> 
> Now in our tree. I decided to add them in the section for net-next: we
> are close to the merge window, and linked to the comment from patch 1,
> it is certainly safer to delay the backport to stable a bit.
> 
> New patches for t/upstream:
> - 0b324b1e22a0: mptcp: pm: in-kernel: usable client side with C-flag
> - b366bcbbad02: "squashed" patch 1/10 in "mptcp: pm: in-kernel: usable
> client side with C-flag"
> - c3ca688abf65: selftests: mptcp: join: validate C-flag + def limit
> - Results: fe9c68017366..8a1a30937c29 (export)

I forgot the last bit:

- Results: fe9c68017366..169aef388767 (export)

Tests are now in progress:

- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/df63a09d28d2808cbe27f96a1937ad904035d2d6/checks

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.