Re: [PATCH V33 27/30] lockdown: Print current->comm in restriction messages
From: Kees Cook <hidden>
Date: 2019-06-21 04:09:42
Also in:
lkml
On Thu, Jun 20, 2019 at 06:19:38PM -0700, Matthew Garrett wrote:
quoted hunk ↗ jump to hunk
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@redhat.com> Signed-off-by: Matthew Garrett <redacted> --- security/lockdown/lockdown.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)diff --git a/security/lockdown/lockdown.c b/security/lockdown/lockdown.c index 14edc475d75c..408f0048f8a2 100644 --- a/security/lockdown/lockdown.c +++ b/security/lockdown/lockdown.c@@ -80,8 +80,8 @@ early_param("lockdown", lockdown_param); static int lockdown_is_locked_down(enum lockdown_reason what) { if ((kernel_locked_down >= what) && lockdown_reasons[what]) - pr_notice("Lockdown: %s is restricted; see man kernel_lockdown.7\n", - lockdown_reasons[what]); + pr_notice("Lockdown: %s: %s is restricted; see man kernel_lockdown.7\n", + current->comm, lockdown_reasons[what]); return (kernel_locked_down >= what); }
Maybe needs ratelimiting?
-- 2.22.0.410.gd8fdbe21b5-goog
-- Kees Cook