On Mon, 10 Feb 2020 12:56:31 +0300 Konstantin Khlebnikov <khlebnikov@xxxxxxxxxxxxxx> wrote:
CONFIG_TEST_LOCKUP=m adds module "test_lockup" that helps to make sure
that watchdogs and lockup detectors are working properly.
Now we'll get test robot reports "hey this makes my kernel lock up" ;)
Is there any way in which we can close the loop here? Add a
tools/testing/selftests script which loads the module, attempts to
trigger a lockup and then checks whether it happened as expected?
Sounds tricky.