asymmetric_keys: log on fatal failures in PE/pkcs7
authorRobbie Harwood <rharwood@redhat.com>
Mon, 20 Feb 2023 17:12:54 +0000 (12:12 -0500)
committerDavid Howells <dhowells@redhat.com>
Tue, 21 Mar 2023 16:23:56 +0000 (16:23 +0000)
commit3584c1dbfffdabf8e3dc1dd25748bb38dd01cd43
tree1b88c30a35cc142ef24a60f8dc50ac5720040055
parent4fc5c74dde69a7eda172514aaeb5a7df3600adb3
asymmetric_keys: log on fatal failures in PE/pkcs7

These particular errors can be encountered while trying to kexec when
secureboot lockdown is in place.  Without this change, even with a
signed debug build, one still needs to reboot the machine to add the
appropriate dyndbg parameters (since lockdown blocks debugfs).

Accordingly, upgrade all pr_debug() before fatal error into pr_warn().

Signed-off-by: Robbie Harwood <rharwood@redhat.com>
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Jarkko Sakkinen <jarkko@kernel.org>
cc: Eric Biederman <ebiederm@xmission.com>
cc: Herbert Xu <herbert@gondor.apana.org.au>
cc: keyrings@vger.kernel.org
cc: linux-crypto@vger.kernel.org
cc: kexec@lists.infradead.org
Link: https://lore.kernel.org/r/20230220171254.592347-3-rharwood@redhat.com/
crypto/asymmetric_keys/pkcs7_verify.c
crypto/asymmetric_keys/verify_pefile.c