netdev - Re: [TEST] mptcp-connect

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: <20250113114406.566f1072@kernel.org>
Date: Mon, 13 Jan 2025 11:44:06 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Matthieu Baerts <matttbe@...nel.org>
Cc: Netdev <netdev@...r.kernel.org>, MPTCP Linux <mptcp@...ts.linux.dev>
Subject: Re: [TEST] mptcp-connect

On Mon, 13 Jan 2025 17:08:02 +0100 Matthieu Baerts wrote:
> It was not easy to reproduce it, but Paolo managed to find a fix for it [1]!
> 
> Out of curiosity, is the netdev CI not too overloaded? To reproduce this
> issue on my side, the host had to be quite busy: not dying with
> stress-ng using all resources, but still competing with many other
> processes, e.g. a kernel compilation running in parallel. I'm not
> complaining here, because this situation helped finding this important
> issue, but just curious about what to expect, especially for more
> "sensitive" tests :)

The tests my overlap with other workers still building their kernel.
ccache is enabled.

> On the MPTCP CI, some unessarry KConfig are disabled and ccache is used
> to reduce the build time. Also, RETPOLINE is disabled (+ vng --append
> mitigations=off) to save some CPU cycles during the tests.

Could help. Let's put it on the list of things to do once we migrate
the CI to a public set of hosts :)