From: Greg KH <gregkh@linuxfoundation.org>
To: Andrew Delgadilo <adelg@google.com>
Cc: Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
dylanbhatch@google.com, sashalevin@google.com,
gthelen@google.com
Subject: Re: [PATCH] selftests: Add a taint selftest
Date: Wed, 24 Aug 2022 07:51:54 +0200 [thread overview]
Message-ID: <YwW8eo1rbo9tmpVK@kroah.com> (raw)
In-Reply-To: <YwWx07EbaB90jDUN@kroah.com>
On Wed, Aug 24, 2022 at 07:06:27AM +0200, Greg KH wrote:
> On Tue, Aug 23, 2022 at 09:19:58PM +0000, Andrew Delgadilo wrote:
> > From: Andrew Delgadillo <adelg@google.com>
> >
> > When testing a kernel, one of the earliest signals one can get is if a
> > kernel has become tainted. For example, an organization might be
> > interested in mass testing commits on their hardware. An obvious first
> > step would be to make sure every commit boots, and a next step would be
> > to make sure there are no warnings/crashes/lockups, hence the utility of
> > a taint test.
>
> What's wrong with the tools/debugging/kernel-chktaint script?
>
> Why do we need another "get what the taint status is" program?
Ah, looks like that script should probably be changed to return an error
code if a taint is found, but that should be a simpler patch rather than
create a whole new script.
thanks,
greg k-h
prev parent reply other threads:[~2022-08-24 5:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 21:19 [PATCH] selftests: Add a taint selftest Andrew Delgadilo
2022-08-24 5:06 ` Greg KH
2022-08-24 5:50 ` Andrew Delgadillo
2022-08-24 6:22 ` Greg KH
2022-08-24 5:51 ` Greg KH [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=YwW8eo1rbo9tmpVK@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adelg@google.com \
--cc=dylanbhatch@google.com \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sashalevin@google.com \
--cc=shuah@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox