24 Aug
2022
24 Aug
'22
5:06 a.m.
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?
thanks,
greg k-h