diff options
| author | Robbie Harwood <rharwood@redhat.com> | 2023-02-20 12:12:54 -0500 |
|---|---|---|
| committer | David Howells <dhowells@redhat.com> | 2023-03-21 16:23:56 +0000 |
| commit | a2bb96ca05091240892a34519b8570d0b3dedfc8 (patch) | |
| tree | 9bc55ebaec115d34c870db1d09fc9e6352ba54b1 /crypto/proc.c | |
| parent | 77a72887977a25cd49e2ab8451a43cb5c1f41c59 (diff) | |
| download | linux-crypto-a2bb96ca05091240892a34519b8570d0b3dedfc8.tar.gz linux-crypto-a2bb96ca05091240892a34519b8570d0b3dedfc8.zip | |
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/ # v2
Diffstat (limited to 'crypto/proc.c')
0 files changed, 0 insertions, 0 deletions