David Gow c272612cb4 kunit: Taint the kernel when KUnit tests are run ... Make KUnit trigger the new TAINT_TEST taint when any KUnit test is run. Due to KUnit tests not being intended to run on production systems, and potentially causing problems (or security issues like leaking kernel addresses), the kernel's state should not be considered safe for production use after KUnit tests are run. This both marks KUnit modules as test modules using MODULE_INFO() and manually taints the kernel when tests are run (which catches builtin tests). Acked-by: Luis Chamberlain <mcgrof@kernel.org> Tested-by: Daniel Latypov <dlatypov@google.com> Reviewed-by: Brendan Higgins <brendanhiggins@google.com> Signed-off-by: David Gow <davidgow@google.com> Tested-by: Maíra Canal <mairacanal@riseup.net> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>		2022-07-01 16:38:43 -06:00
..
assert.h	kunit: factor out str constants from binary assertion structs	2022-01-31 11:55:39 -07:00
resource.h	kunit: Rework kunit_resource allocation policy	2022-05-12 11:14:39 -06:00
test-bug.h	kunit: fix -Wunused-function warning for __kunit_fail_current_test	2021-04-06 15:22:39 -06:00
test.h	kunit: Taint the kernel when KUnit tests are run	2022-07-01 16:38:43 -06:00
try-catch.h	kunit: hide unexported try-catch interface in try-catch-impl.h	2020-01-09 16:42:09 -07:00