Kees Cook d46e58ef77 lkdtm/bugs: Check that a per-task stack canary exists ... Introduce REPORT_STACK_CANARY to check for differing stack canaries between two processes (i.e. that an architecture is correctly implementing per-task stack canaries), using the task_struct canary as the hint to locate in the stack. Requires that one of the processes being tested not be pid 1. Cc: Ard Biesheuvel <ardb@kernel.org> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Kees Cook <keescook@chromium.org> Link: https://lore.kernel.org/r/20211022223826.330653-3-keescook@chromium.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2021-10-25 09:13:46 +02:00
..
bugs.c	lkdtm/bugs: Check that a per-task stack canary exists	2021-10-25 09:13:46 +02:00
cfi.c	lkdtm: Add CONFIG hints in errors where possible	2021-06-24 15:32:08 +02:00
core.c	lkdtm/bugs: Check that a per-task stack canary exists	2021-10-25 09:13:46 +02:00
fortify.c	lkdtm/fortify: Consolidate FORTIFY_SOURCE tests	2021-08-18 22:28:51 +02:00
heap.c	lkdtm/heap: Avoid __alloc_size hint warning for VMALLOC_LINEAR_OVERFLOW	2021-08-18 22:28:51 +02:00
lkdtm.h	lkdtm/bugs: Check that a per-task stack canary exists	2021-10-25 09:13:46 +02:00
Makefile
perms.c
powerpc.c
refcount.c
rodata.c
stackleak.c	lkdtm: Add CONFIG hints in errors where possible	2021-06-24 15:32:08 +02:00
usercopy.c	lkdtm: Add CONFIG hints in errors where possible	2021-06-24 15:32:08 +02:00