Commit fcff71fd authored by Thomas Weißschuh's avatar Thomas Weißschuh Committed by Eric Biggers
Browse files

lib/crypto: tests: polyval_kunit: Increase iterations for preparekey in IRQs 



On my development machine the generic, memcpy()-only implementation of
polyval_preparekey() is too fast for the IRQ workers to actually fire.
The test fails.

Increase the iterations to make the test more robust.
The test will run for a maximum of one second in any case.

[EB: This failure was already fixed by commit c31f4aa8 ("kunit:
Enforce task execution in {soft,hard}irq contexts").  I'm still applying
this patch too, since the iteration count in this test made its running
time much shorter than the other similar ones.]

Fixes: b3aed551 ("lib/crypto: tests: Add KUnit tests for POLYVAL")
Signed-off-by: default avatarThomas Weißschuh <thomas.weissschuh@linutronix.de>
Link: https://lore.kernel.org/r/20260102-kunit-polyval-fix-v1-1-5313b5a65f35@linutronix.de


Signed-off-by: default avatarEric Biggers <ebiggers@kernel.org>
parent 9ace4753

lib/crypto/tests/polyval_kunit.c

+1 −1
Original line number Diff line number Diff line
@@ -183,7 +183,7 @@ static void test_polyval_preparekey_in_irqs(struct kunit *test) 


	rand_bytes(state.raw_key, sizeof(state.raw_key));

	polyval_preparekey(&state.expected_key, state.raw_key);

	kunit_run_irq_test(test, polyval_irq_test_func, 20000, &state);

	kunit_run_irq_test(test, polyval_irq_test_func, 200000, &state);

}



static int polyval_suite_init(struct kunit_suite *suite)