linux-kernel - Re: [PATCH net v2 0/2] selftests: mptcp: connect: cover alt modes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9175b633-b61f-4ca0-9023-c99dff4f53f0@kernel.org>
Date: Fri, 18 Jul 2025 01:49:24 +0200
From: Matthieu Baerts <matttbe@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>
Cc: mptcp@...ts.linux.dev, Mat Martineau <martineau@...nel.org>,
 Geliang Tang <geliang@...nel.org>, "David S. Miller" <davem@...emloft.net>,
 Eric Dumazet <edumazet@...gle.com>, Simon Horman <horms@...nel.org>,
 Shuah Khan <shuah@...nel.org>, Christoph Paasch <cpaasch@...nai.com>,
 Davide Caratti <dcaratti@...hat.com>, Florian Westphal <fw@...len.de>,
 linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
 linux-kselftest@...r.kernel.org
Subject: Re: [PATCH net v2 0/2] selftests: mptcp: connect: cover alt modes

Hi Jakub,

On 17/07/2025 16:42, Jakub Kicinski wrote:
> On Wed, 16 Jul 2025 18:35:11 +0200 Matthieu Baerts wrote:
>>>> And just to be sure, no CPU or IO overload at that moment? I didn't see
>>>> such errors reported by our CI, but I can try to reproduce them locally
>>>> in different conditions.  
>>>
>>> None that I can see. The test run ~10min after all the builds completed,
>>> and we wait now for the CPU load to die down and writeback to finish
>>> before we kick off VMs. The VMs for various tests are running at that
>>> point, the CPU util averaged across cores is 66%.  
>>
>> Thank you for having checked, and for the explanations!
>>
>> OK, so maybe running stress-ng in parallel to be able to reproduce the
>> issue might not help. We will investigate.
> 
> connect tests failed again overnight. Now I see why Paolo was
> responding on Eric's series, that seems like a more likely culprit..

Good point, Paolo was certainly right, as always :)

We do need to investigate. Note that it might be hard for me to do that
the next few days as I'm travelling for work, but we are tracking the issue:

  https://github.com/multipath-tcp/mptcp_net-next/issues/574

I see that you already marked the mptcp-connect-sh selftest as ignored,
so I guess we are not causing other troubles with the CI. (We could then
also apply this series here and ignore the new tests, but it is also
fine for me to wait.)

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