[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221109025019.1855-2-linux@weissschuh.net>
Date: Wed, 9 Nov 2022 03:50:17 +0100
From: Thomas Weißschuh <linux@...ssschuh.net>
To: Mickaël Salaün <mic@...ikod.net>,
David Howells <dhowells@...hat.com>,
David Woodhouse <dwmw2@...radead.org>,
Jarkko Sakkinen <jarkko@...nel.org>,
Eric Snowberg <eric.snowberg@...cle.com>
Cc: Thomas Weißschuh <linux@...ssschuh.net>,
keyrings@...r.kernel.org, linux-kernel@...r.kernel.org,
Mark Pearson <markpearson@...ovo.com>,
linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org
Subject: [PATCH v2 1/3] certs: log more information on blacklist error
Without this information these logs are not actionable.
Fixes: 6364d106e041 ("certs: Allow root user to append signed hashes to the blacklist keyring")
Signed-off-by: Thomas Weißschuh <linux@...ssschuh.net>
---
certs/blacklist.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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;
--
2.38.1
Powered by blists - more mailing lists