lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <20190404003249.14356-26-matthewgarrett@google.com> Date: Wed, 3 Apr 2019 17:32:47 -0700 From: Matthew Garrett <matthewgarrett@...gle.com> To: jmorris@...ei.org Cc: linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org, dhowells@...hat.com, linux-api@...r.kernel.org, luto@...nel.org, Matthew Garrett <matthewgarrett@...gle.com>, Matthew Garrett <mjg59@...gle.com> Subject: [PATCH V32 25/27] lockdown: Print current->comm in restriction messages Print the content of current->comm in messages generated by lockdown to indicate a restriction that was hit. This makes it a bit easier to find out what caused the message. The message now patterned something like: Lockdown: <comm>: <what> is restricted; see man kernel_lockdown.7 Signed-off-by: David Howells <dhowells@...hat.com> Signed-off-by: Matthew Garrett <mjg59@...gle.com> --- security/lock_down.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/security/lock_down.c b/security/lock_down.c index 9913fff09ad0..2659722784cc 100644 --- a/security/lock_down.c +++ b/security/lock_down.c @@ -70,8 +70,8 @@ bool __kernel_is_locked_down(const char *what, enum lockdown_level level, bool first) { if ((kernel_locked_down >= level) && what && first) - pr_notice("Lockdown: %s is restricted; see man kernel_lockdown.7\n", - what); + pr_notice("Lockdown: %s: %s is restricted; see man kernel_lockdown.7\n", + current->comm, what); return (kernel_locked_down >= level); } EXPORT_SYMBOL(__kernel_is_locked_down); -- 2.21.0.392.gf8f6787159e-goog
Powered by blists - more mailing lists