30 Apr
2022
30 Apr
'22
5:50 a.m.
On Sat, Apr 30, 2022 at 11:00:19AM +0800, David Gow wrote:
KUnit tests are not supposed to run on production systems: they may do deliberately illegal things to trigger errors, and have security implications (assertions will often deliberately leak kernel addresses).
Add a new taint type, TAINT_KUNIT to signal that a KUnit test has been run. This will be printed as 'N' (for kuNit, as K, U and T were already taken).
This should discourage people from running KUnit tests on production systems, and to make it easier to tell if tests have been run accidentally (by loading the wrong configuration, etc.)
Signed-off-by: David Gow davidgow@google.com
Reviewed-by: Greg Kroah-Hartman gregkh@linuxfoundation.org