Re: [PATCH mptcp-net] mptcp: fallback earlier on simult connection

[Matthieu Baerts <matttbe@kernel.org>]

Hi Paolo,

On 01/12/2025 12:10, Paolo Abeni wrote:
> On 11/28/25 2:35 PM, MPTCP CI wrote:
>> Thank you for your modifications, that's great!
>>
>> Our CI did some validations and here is its report:
>>
>> - KVM Validation: normal (except selftest_mptcp_join): Unstable: 2 failed test(s): packetdrill_syscalls selftest_simult_flows 🔴
>> - KVM Validation: normal (only selftest_mptcp_join): Success! ✅
>> - KVM Validation: debug (except selftest_mptcp_join): Unstable: 1 failed test(s): packetdrill_syscalls 🔴
>> - KVM Validation: debug (only selftest_mptcp_join): Success! ✅
>> - KVM Validation: btf-normal (only bpftest_all): Success! ✅
>> - KVM Validation: btf-debug (only bpftest_all): Unstable: 1 failed test(s): bpftest_test_progs_mptcp 🔴
>> - Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/19764025304
> 
> As mentioned, pktdrill failures are expected - test need to be updated.
> 
> The simult flows and btf failures are unexpected, but looks unrelated
> from this patch.

Thank you for having checked! (Sorry, I'm lagging a bit behind)

Regarding the simult_flows tests, the last job checking the sync with
net/net-next also has a failure:

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

So not a regression due to your patch, but I hope there is not one due
to other changes!

(The last job also mentioned issues with a new packetdrill test, I'm
going to look at it, then apply your patch!)

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