d46e58ef77
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>
12 lines
313 B
Plaintext
12 lines
313 B
Plaintext
CONFIG_LKDTM=y
|
|
CONFIG_DEBUG_LIST=y
|
|
CONFIG_SLAB_FREELIST_HARDENED=y
|
|
CONFIG_FORTIFY_SOURCE=y
|
|
CONFIG_HARDENED_USERCOPY=y
|
|
# CONFIG_HARDENED_USERCOPY_FALLBACK is not set
|
|
CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT=y
|
|
CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y
|
|
CONFIG_UBSAN_BOUNDS=y
|
|
CONFIG_UBSAN_TRAP=y
|
|
CONFIG_STACKPROTECTOR_STRONG=y
|