summaryrefslogtreecommitdiffstats
path: root/certs
diff options
context:
space:
mode:
authorThomas Weißschuh <linux@weissschuh.net>2023-01-09 23:59:41 +0000
committerJarkko Sakkinen <jarkko@kernel.org>2023-02-13 10:11:20 +0200
commit06b53b02945e3021addc6af2da3ac999d2221d23 (patch)
treeba4020729fc2e00de5832ecb46173fae04e51646 /certs
parent4d2732882703791ea4b670df433f88fc4b40a5cb (diff)
downloadlinux-06b53b02945e3021addc6af2da3ac999d2221d23.tar.gz
linux-06b53b02945e3021addc6af2da3ac999d2221d23.tar.bz2
linux-06b53b02945e3021addc6af2da3ac999d2221d23.zip
certs: make blacklisted hash available in klog
One common situation triggering this log statement are duplicate hashes reported by the system firmware. These duplicates should be removed from the firmware. Without logging the blacklisted hash triggering the issue however the users can not report it properly to the firmware vendors and the firmware vendors can not easily see which specific hash is duplicated. While changing the log message also use the dedicated ERR_PTR format placeholder for the returned error value. Signed-off-by: Thomas Weißschuh <linux@weissschuh.net> Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
Diffstat (limited to 'certs')
-rw-r--r--certs/blacklist.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/certs/blacklist.c b/certs/blacklist.c
index 41f10601cc72..6e260c4b6a19 100644
--- a/certs/blacklist.c
+++ b/certs/blacklist.c
@@ -192,7 +192,7 @@ static int mark_raw_hash_blacklisted(const char *hash)
KEY_ALLOC_NOT_IN_QUOTA |
KEY_ALLOC_BUILT_IN);
if (IS_ERR(key)) {
- pr_err("Problem blacklisting hash (%ld)\n", PTR_ERR(key));
+ pr_err("Problem blacklisting hash %s: %pe\n", hash, key);
return PTR_ERR(key);
}
return 0;