linux-kernel - Re: [PATCH/RFC] kunit/rtc: Add real support for very slow tests

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: <20250723161038ab6abef0@mail.local>
Date: Wed, 23 Jul 2025 18:10:38 +0200
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: David Gow <davidgow@...gle.com>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
	Brendan Higgins <brendan.higgins@...ux.dev>,
	Rae Moar <rmoar@...gle.com>, linux-kselftest@...r.kernel.org,
	kunit-dev@...glegroups.com, linux-rtc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH/RFC] kunit/rtc: Add real support for very slow tests

On 28/03/2025 16:06:52+0800, David Gow wrote:
> I'll get around to extending this to allow the "base timeout" to be
> configurable as a command-line option, too, if this seems like a good
> way to go.
> 
> >   3. Mark rtc_time64_to_tm_test_date_range_1000 slow,
> >   4. Mark rtc_time64_to_tm_test_date_range_160000 very slow.
> 
> Hmm... these are definitely fast enough on my "modern" machine that
> they probably only warrant "slow", not "very slow". But given they're
> definitely causing problems on older machines, I'm happy to go with
> marking the large ones very slow. (I've been waiting for them for
> about 45 minutes so far on my 486.)

Note that as discussed elsewhere, I'm open to simply remove
rtc_time64_to_tm_test_date_range_160000. It was a nice proof that he change was
working at the time but I don't think it is necessary to check this range.

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com