Kees Cook 1ee170ea3f lkdtm: Split WARNING into separate tests ... There are three paths through the kernel code exception logging: - BUG (no configurable printk message) - WARN_ON (no configurable printk message) - WARN (configurable printk message) LKDTM was not testing WARN_ON(). This is needed to evaluate the placement of the "cut here" line, which needs special handling in each of the three exceptions (and between architectures that implement instruction exceptions to implement the code exceptions). Signed-off-by: Kees Cook <keescook@chromium.org>		2019-08-19 11:13:21 -07:00
..
bugs.c	lkdtm: Split WARNING into separate tests	2019-08-19 11:13:21 -07:00
cfi.c	lkdtm: Add Control Flow Integrity test	2019-08-12 15:28:51 -07:00
core.c	lkdtm: Split WARNING into separate tests	2019-08-19 11:13:21 -07:00
heap.c	lkdtm/heap: add tests for freelist hardening	2019-07-12 11:05:41 -07:00
lkdtm.h	lkdtm: Split WARNING into separate tests	2019-08-19 11:13:21 -07:00
Makefile	lkdtm: Add Control Flow Integrity test	2019-08-12 15:28:51 -07:00
perms.c	lkdtm: Add tests for NULL pointer dereference	2019-01-09 12:00:31 -08:00
refcount.c
rodata.c
stackleak.c	lkdtm: Add a test for STACKLEAK	2018-09-04 10:35:47 -07:00
usercopy.c	lkdtm/usercopy: Moves the KERNEL_DS test to non-canonical	2019-04-07 10:38:31 -07:00