]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
selftests: Print the test we're running to /dev/kmsg
authorMichael Ellerman <mpe@ellerman.id.au>
Fri, 23 Mar 2018 09:44:27 +0000 (20:44 +1100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 30 May 2018 05:50:43 +0000 (07:50 +0200)
commit3feab927bb324ffd673825f6f3911f61775ed9d3
tree70a99755fad41a8158d10f95df14db9c0b729fd3
parent98b219800a8fc5ce5da5eb597f1fbd8e010ae87a
selftests: Print the test we're running to /dev/kmsg

[ Upstream commit 88893cf787d3062c631cc20b875068eb11756e03 ]

Some tests cause the kernel to print things to the kernel log
buffer (ie. printk), in particular oops and warnings etc. However when
running all the tests in succession it's not always obvious which
test(s) caused the kernel to print something.

We can narrow it down by printing which test directory we're running
in to /dev/kmsg, if it's writable.

Example output:

  [  170.149149] kselftest: Running tests in powerpc
  [  305.300132] kworker/dying (71) used greatest stack depth: 7776 bytes
                 left
  [  808.915456] kselftest: Running tests in pstore

Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
tools/testing/selftests/Makefile