From: Kees Cook <keescook@chromium.org>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Petr Mladek <pmladek@suse.com>,
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: Tue, 11 Feb 2020 11:21:29 -0800 [thread overview]
Message-ID: <202002111120.91782E0686@keescook> (raw)
In-Reply-To: <5e5ee6b7-68a9-1bcc-66c5-814e40a627be@yandex-team.ru>
On Tue, Feb 11, 2020 at 03:57:42PM +0300, Konstantin Khlebnikov wrote:
> On 11/02/2020 04.26, Kees Cook wrote:
> > On Mon, Feb 10, 2020 at 12:56:31PM +0300, Konstantin Khlebnikov wrote:
> > > CONFIG_TEST_LOCKUP=m adds module "test_lockup" that helps to make sure
> > > that watchdogs and lockup detectors are working properly.
> >
> > Isn't this all already possible with CONFIG_LKDTM ?
>
> Yep, LKDTM covers some cases. But they are unrecoverable.
>
> It seems LKDTM is more like a fixed set of unit tests while
> test_lockup is a flexible tool for stress load.
Okay, cool. I just wanted to make sure you'd seen LKDTM and there wasn't
too much wheel-reinvention happening. :) Thanks for checking!
-Kees
--
Kees Cook
prev parent reply other threads:[~2020-02-11 19:21 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
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 [this message]
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=202002111120.91782E0686@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=dmtrmonakhov@yandex-team.ru \
--cc=gregkh@linuxfoundation.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.