Matthew Garrett b602614a81 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@redhat.com> Signed-off-by: Matthew Garrett <mjg59@google.com> Reviewed-by: Kees Cook <keescook@chromium.org> Signed-off-by: James Morris <jmorris@namei.org>		2019-08-19 21:54:17 -07:00
..
array.c	fs/proc/array.c: allow reporting eip/esp for all coredumping threads	2019-06-29 16:43:44 +08:00
base.c	proc: remove useless d_is_dir() check	2019-06-27 12:25:09 +02:00
cmdline.c
consoles.c
cpuinfo.c
devices.c
fd.c
fd.h
generic.c
inode.c
internal.h
interrupts.c
Kconfig
kcore.c	lockdown: Print current->comm in restriction messages	2019-08-19 21:54:17 -07:00
kmsg.c
loadavg.c
Makefile
meminfo.c
namespaces.c
nommu.c
page.c
proc_net.c
proc_sysctl.c
proc_tty.c
root.c
self.c
softirqs.c
stat.c
task_mmu.c
task_nommu.c
thread_self.c
uptime.c
util.c
version.c
vmcore.c