- Sep 07, 2022
-
-
Joe Fradley authored
Commit c272612c ("kunit: Taint the kernel when KUnit tests are run") added a new taint flag for when in-kernel tests run. This commit adds recognition of this new flag in kernel-chktaint. With this change the correct reason will be reported if the kernel is tainted because of a test run. Amended Commit log: Shuah Khan <skhan@linuxfoundation.org> Reviewed-by:
David Gow <davidgow@google.com> Signed-off-by:
Joe Fradley <joefradley@google.com> Reviewed-by:
Brendan Higgins <brendanhiggins@google.com> Signed-off-by:
Shuah Khan <skhan@linuxfoundation.org>
-
- Jun 14, 2021
-
-
Colin Ian King authored
There is a double "the" in a message in kernel-chktaint, fix it. Signed-off-by:
Colin Ian King <colin.king@canonical.com> Link: https://lore.kernel.org/r/20210613202059.80403-1-colin.king@canonical.com Signed-off-by:
Jonathan Corbet <corbet@lwn.net>
-
- Apr 08, 2021
-
-
Masanari Iida authored
This patch fixes a spelling typo in kernel-chktaint Signed-off-by:
Masanari Iida <standby24x7@gmail.com> Acked-by:
Randy Dunlap <rdunlap@infradead.org> Link: https://lore.kernel.org/r/20210402070514.336376-1-standby24x7@gmail.com Signed-off-by:
Jonathan Corbet <corbet@lwn.net>
-
- Dec 08, 2020
-
-
Mathieu Chouquet-Stringer authored
Here's a patch updating the meaning of TAINT_CPU_OUT_OF_SPEC after Borislav introduced changes in a7e1f67e and upcoming patches in tip. TAINT_CPU_OUT_OF_SPEC now means a bit more what it implies as the flag isn't set just because of a CPU misconfiguration or mismatch. Historically it was for SMP kernel oops on an officially SMP incapable processor but now it also covers CPUs whose MSRs have been incorrectly poked at from userspace, drivers being used on non supported architectures, broken firmware, mismatched CPUs, ... Update documentation and script to reflect that. Signed-off-by:
Mathieu Chouquet-Stringer <me@mathieu.digital> Link: https://lore.kernel.org/r/20201202153244.709752-1-me@mathieu.digital Signed-off-by:
Jonathan Corbet <corbet@lwn.net>
-
- Jan 09, 2019
-
-
Thorsten Leemhuis authored
Add a script to the tools/ directory that shows if or why the running kernel was tainted. The script was mostly written by Randy Dunlap; I enhanced the script a bit. There does not appear to be a good home for this script. so create tools/debugging for tools of this nature. Signed-off-by:
Randy Dunlap <rdunlap@infradead.org> Signed-off-by:
Thorsten Leemhuis <linux@leemhuis.info> [ jc: fixed conflicts, rewrote changelog ] Signed-off-by:
Jonathan Corbet <corbet@lwn.net>
-