linux-uconsole/tools/testing
Michael Ellerman e1448fac67 selftests: Print the test we're running to /dev/kmsg
[ Upstream commit 88893cf787 ]

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>
2018-05-30 07:49:10 +02:00
..
fault-injection fault-injection: fix failcmd.sh warning 2012-07-31 18:42:38 -07:00
ktest ktest: Fix child exit code processing 2017-03-15 09:57:13 +08:00
nvdimm tools/testing/nvdimm: fix SIGTERM vs hotplug crash 2016-09-07 08:32:36 +02:00
selftests selftests: Print the test we're running to /dev/kmsg 2018-05-30 07:49:10 +02:00