29e3ea8cbd
Previously when mapping kernel memory on radix, no ptesync was included which would periodically lead to unhandled spurious faults. Mapping kernel memory is used when code patching with Strict RWX enabled. As suggested by Chris Riedl, turning ftrace on and off does a large amount of code patching so is a convenient way to see this kind of fault. Add a selftest to try and trigger this kind of a spurious fault. It tests for 30 seconds which is usually long enough for the issue to show up. Signed-off-by: Jordan Niethe <jniethe5@gmail.com> [mpe: Rename it to better reflect what it does, rather than the symptom] Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Link: https://lore.kernel.org/r/20210208032957.1232102-2-jniethe5@gmail.com
36 lines
1012 B
Makefile
36 lines
1012 B
Makefile
# SPDX-License-Identifier: GPL-2.0
|
|
noarg:
|
|
$(MAKE) -C ../
|
|
|
|
TEST_GEN_PROGS := hugetlb_vs_thp_test subpage_prot prot_sao segv_errors wild_bctr \
|
|
large_vm_fork_separation bad_accesses pkey_exec_prot \
|
|
pkey_siginfo stack_expansion_signal stack_expansion_ldst
|
|
TEST_PROGS := stress_code_patching.sh
|
|
|
|
TEST_GEN_PROGS_EXTENDED := tlbie_test
|
|
TEST_GEN_FILES := tempfile
|
|
|
|
top_srcdir = ../../../../..
|
|
include ../../lib.mk
|
|
|
|
$(TEST_GEN_PROGS): ../harness.c ../utils.c
|
|
|
|
$(OUTPUT)/prot_sao: ../utils.c
|
|
|
|
$(OUTPUT)/wild_bctr: CFLAGS += -m64
|
|
$(OUTPUT)/large_vm_fork_separation: CFLAGS += -m64
|
|
$(OUTPUT)/bad_accesses: CFLAGS += -m64
|
|
$(OUTPUT)/pkey_exec_prot: CFLAGS += -m64
|
|
$(OUTPUT)/pkey_siginfo: CFLAGS += -m64
|
|
|
|
$(OUTPUT)/stack_expansion_signal: ../utils.c ../pmu/lib.c
|
|
|
|
$(OUTPUT)/stack_expansion_ldst: CFLAGS += -fno-stack-protector
|
|
$(OUTPUT)/stack_expansion_ldst: ../utils.c
|
|
|
|
$(OUTPUT)/tempfile:
|
|
dd if=/dev/zero of=$@ bs=64k count=1
|
|
|
|
$(OUTPUT)/tlbie_test: LDLIBS += -lpthread
|
|
$(OUTPUT)/pkey_siginfo: LDLIBS += -lpthread
|