On Sat, Aug 13, 2022 at 06:14:43PM -0500, Robert Elliott wrote: > This userspace command: > modprobe tcrypt > or > modprobe tcrypt mode=0 > > runs all the tcrypt test cases numbered <200 (i.e., all the > test cases calling tcrypt_test() and returning return values). > > Tests are sparsely numbered from 0 to 1000. For example: > modprobe tcrypt mode=12 > tests sha512, and > modprobe tcrypt mode=152 > tests rfc4543(gcm(aes))) - AES-GCM as GMAC > > The test manager generates WARNING crashdumps every time it attempts > a test using an algorithm that is not available (not built-in to the > kernel or available as a module): Note that this is only a problem because tcrypt calls alg_test() directly. The normal way that alg_test() gets called is for the registration-time self-test. It's not clear to me why tcrypt calls alg_test() directly; the registration-time test should be enough. Herbert, do you know? - Eric
