linux-kernel - Re: [PATCH] selftests/mm: Increase timeout from 180 to 900 seconds

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] [day] [month] [year] [list]

Message-ID: <b1fe7706-cfce-4c8c-ae21-b2ddd03a0917@amd.com>
Date: Tue, 10 Jun 2025 10:58:47 +0530
From: Shivank Garg <shivankg@....com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: shuah@...nel.org, linux-mm@...ck.org, linux-kselftest@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] selftests/mm: Increase timeout from 180 to 900 seconds



On 6/10/2025 4:37 AM, Andrew Morton wrote:
> On Mon, 9 Jun 2025 12:06:07 +0000 Shivank Garg <shivankg@....com> wrote:
> 
>> The mm selftests are timing out with the current 180-second limit.
>> Testing shows that run_vmtests.sh takes approximately 11 minutes
>> (664 seconds) to complete.
>>
>> Increase the timeout to 900 seconds (15 minutes) to provide sufficient
>> buffer for the tests to complete successfully.
>>
>> ...
>>
>> --- a/tools/testing/selftests/mm/settings
>> +++ b/tools/testing/selftests/mm/settings
>> @@ -1 +1 @@
>> -timeout=180
>> +timeout=900
> 
> Gee, that's a bit crude, isn't it.  I have a laptop which will need 90000 ;)
> 
> I guess it's better than it was before.  Some sort of smarter monitor
> of ongoing activity can be bothered about later.
> 
900s is crude, and I can imagine some systems needing even more time!
I think the real issue is run_vmtests.sh bundles many tests together. Most finish quickly but few (e.g. compaction) tests take significant time.
I agree that a smarter approach with per-test timeouts would be better.

Thanks,
Shivank