Re: [PATCH mptcp-next 0/2] fixes for "mptcp: receive path improvement" v3

[Matthieu Baerts <matttbe@kernel.org>]

Hi Paolo,

On 22/09/2025 10:43, Paolo Abeni wrote:
> On 9/22/25 10:35 AM, Matthieu Baerts wrote:
>> Hi Geliang, Paolo,
>>
>> On 20/09/2025 05:44, Geliang Tang wrote:
>>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>>
>>> Try to fix errors reported by CI.
>>
>> @Geliang: Thank you! The modifications make sense to me.
>>
>> @Paolo: do you want to send the v4 series to netdev directly?
> 
> I also have some questions :)
> 
> Does this follow-up address the CI failures for good?

When I sent my email, I noticed Patchew didn't process these patches. I
manually started the CI, it's in progress, but all the mptcp_connect*.sh
tests have passed!

https://github.com/multipath-tcp/mptcp_net-next/actions/runs/17909424668

> I think patch 1-3 could be merged and export and send to netdev. Patch
> 10/10 is possibly a little too invasive at this to enter 6.18 this late.
> I *think* it could wait the next cycles (together with all the pre-req
> and follow-up), but I'm ok to go ahead now, too. (But CI has to be happy
> before sharing on netdev).

Mmh, I would say: because the v6.18 is supposed to be the next LTS, and
syzkaller doesn't seem to complain, I *think* it might be worth it to be
more aligned with what TCP is doing, and send all patches to net-next.
(With or without the small changes suggested by Geliang, up to you, I'm
fine with or without them.)

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