From: Andrew Morton <akpm@linux-foundation.org>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: linux-kernel@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Petr Mladek <pmladek@suse.com>, Kees Cook <keescook@chromium.org>,
Peter Zijlstra <peterz@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Dmitry Monakhov <dmtrmonakhov@yandex-team.ru>
Subject: Re: [PATCH] lib/test_lockup: test module to generate lockups
Date: Mon, 10 Feb 2020 14:41:01 -0800 [thread overview]
Message-ID: <20200210144101.e144335455399d6d84d92370@linux-foundation.org> (raw)
In-Reply-To: <158132859146.2797.525923171323227836.stgit@buzz>
On Mon, 10 Feb 2020 12:56:31 +0300 Konstantin Khlebnikov <khlebnikov@yandex-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.
next prev parent reply other threads:[~2020-02-10 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 9:56 [PATCH] lib/test_lockup: test module to generate lockups Konstantin Khlebnikov
2020-02-10 22:41 ` Andrew Morton [this message]
2020-02-11 13:01 ` Konstantin Khlebnikov
2020-02-11 1:26 ` Kees Cook
2020-02-11 12:57 ` Konstantin Khlebnikov
2020-02-11 19:21 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200210144101.e144335455399d6d84d92370@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dmtrmonakhov@yandex-team.ru \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=sergey.senozhatsky@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.