[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c7e9d2ac-0f6d-31ed-ec00-cc315b1e34f8@yandex-team.ru>
Date: Tue, 11 Feb 2020 16:01:14 +0300
From: Konstantin Khlebnikov <khlebnikov@...dex-team.ru>
To: Andrew Morton <akpm@...ux-foundation.org>
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 11/02/2020 01.41, Andrew Morton wrote:
> 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" ;)
Without module parameters it is completely save and does nothing.
>
> 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.
>
Yes, I'll try to script this.
Powered by blists - more mailing lists