[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200210144101.e144335455399d6d84d92370@linux-foundation.org>
Date: Mon, 10 Feb 2020 14:41:01 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Konstantin Khlebnikov <khlebnikov@...dex-team.ru>
Cc: linux-kernel@...r.kernel.org, Sasha Levin <sashal@...nel.org>,
Petr Mladek <pmladek@...e.com>,
Kees Cook <keescook@...omium.org>,
Peter Zijlstra <peterz@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Dmitry Monakhov <dmtrmonakhov@...dex-team.ru>
Subject: Re: [PATCH] lib/test_lockup: test module to generate lockups
On Mon, 10 Feb 2020 12:56:31 +0300 Konstantin Khlebnikov <khlebnikov@...dex-team.ru> 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.
Powered by blists - more mailing lists