]> git.proxmox.com Git - mirror_ubuntu-bionic-kernel.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)
committerKleber Sacilotto de Souza <kleber.souza@canonical.com>
Mon, 27 Aug 2018 14:40:05 +0000 (16:40 +0200)
commit58657f15d010a8585389fa3c9d8de5113271bad1
tree1939ea745f06a716a9c0375ab54def0fdbdfc0b5
parentf9aa885f548060fa2642ab9a493718bf215954fa
selftests: Print the test we're running to /dev/kmsg

BugLink: http://bugs.launchpad.net/bugs/1786352
[ 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>
Signed-off-by: Kamal Mostafa <kamal@canonical.com>
Signed-off-by: Khalid Elmously <khalid.elmously@canonical.com>
tools/testing/selftests/Makefile