diff options
| author | Eric Biggers <ebiggers@google.com> | 2020-10-26 09:31:12 -0700 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2020-11-06 14:29:10 +1100 |
| commit | 83793cc0613d70185e68b414c97507ce8790a0be (patch) | |
| tree | a1dab48df63f5ef8c14d89b8c57537007d537180 /crypto/rsapubkey.asn1 | |
| parent | f164a97cbca10866edc212d4f60f9e2bd51d1cf2 (diff) | |
| download | linux-crypto-83793cc0613d70185e68b414c97507ce8790a0be.tar.gz linux-crypto-83793cc0613d70185e68b414c97507ce8790a0be.zip | |
crypto: testmgr - WARN on test failure
Currently, by default crypto self-test failures only result in a
pr_warn() message and an "unknown" status in /proc/crypto. Both of
these are easy to miss. There is also an option to panic the kernel
when a test fails, but that can't be the default behavior.
A crypto self-test failure always indicates a kernel bug, however, and
there's already a standard way to report (recoverable) kernel bugs --
the WARN() family of macros. WARNs are noisier and harder to miss, and
existing test systems already know to look for them in dmesg or via
/proc/sys/kernel/tainted.
Therefore, call WARN() when an algorithm fails its self-tests.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/rsapubkey.asn1')
0 files changed, 0 insertions, 0 deletions