34f7f79827
We recently discovered some of our mitigation patching was not safe against other CPUs running concurrently. Add a test which enable/disables all mitigations in a tight loop while also running some stress load. On an unpatched system this almost always leads to an oops and panic/reboot, but we also check if the kernel becomes tainted in case we have a non-fatal oops. Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Link: https://lore.kernel.org/r/20210507064225.1556312-1-mpe@ellerman.id.au
19 lines
475 B
Makefile
19 lines
475 B
Makefile
# SPDX-License-Identifier: GPL-2.0+
|
|
|
|
TEST_GEN_PROGS := rfi_flush entry_flush uaccess_flush spectre_v2
|
|
TEST_PROGS := mitigation-patching.sh
|
|
|
|
top_srcdir = ../../../../..
|
|
|
|
CFLAGS += -I../../../../../usr/include
|
|
|
|
include ../../lib.mk
|
|
|
|
$(TEST_GEN_PROGS): ../harness.c ../utils.c
|
|
|
|
$(OUTPUT)/spectre_v2: CFLAGS += -m64
|
|
$(OUTPUT)/spectre_v2: ../pmu/event.c branch_loops.S
|
|
$(OUTPUT)/rfi_flush: flush_utils.c
|
|
$(OUTPUT)/entry_flush: flush_utils.c
|
|
$(OUTPUT)/uaccess_flush: flush_utils.c
|