aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/testing/selftests/ftrace
diff options
context:
space:
mode:
authorMichael Ellerman <mpe@ellerman.id.au>2020-05-08 16:53:55 +1000
committerShuah Khan <skhan@linuxfoundation.org>2020-05-08 09:45:50 -0600
commitf131d9edc29d527df4b8f6840c340415f559f095 (patch)
tree81af23ff6a76922921dfab631fb9573b16107386 /tools/testing/selftests/ftrace
parentselftests/ftrace: mark irqsoff_tracer.tc test as unresolved if the test module does not exist (diff)
downloadwireguard-linux-f131d9edc29d527df4b8f6840c340415f559f095.tar.xz
wireguard-linux-f131d9edc29d527df4b8f6840c340415f559f095.zip
selftests/lkdtm: Don't clear dmesg when running tests
It is Very Rude to clear dmesg in test scripts. That's because the script may be part of a larger test run, and clearing dmesg potentially destroys the output of other tests. We can avoid using dmesg -c by saving the content of dmesg before the test, and then using diff to compare that to the dmesg afterward, producing a log with just the added lines. Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Acked-by: Kees Cook <keescook@chromium.org> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'tools/testing/selftests/ftrace')
0 files changed, 0 insertions, 0 deletions