|author||Ben Hutchings <email@example.com>||2011-10-24 15:12:28 +0200|
|committer||Rusty Russell <firstname.lastname@example.org>||2011-11-07 07:54:42 +1030|
module,bug: Add TAINT_OOT_MODULE flag for modules not built in-tree
Use of the GPL or a compatible licence doesn't necessarily make the code any good. We already consider staging modules to be suspect, and this should also be true for out-of-tree modules which may receive very little review. Signed-off-by: Ben Hutchings <email@example.com> Reviewed-by: Dave Jones <firstname.lastname@example.org> Acked-by: Greg Kroah-Hartman <email@example.com> Signed-off-by: Rusty Russell <firstname.lastname@example.org> (patched oops-tracing.txt)
Diffstat (limited to 'Documentation')
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/oops-tracing.txt b/Documentation/oops-tracing.txt
index 6fe9001b926..13032c0140d 100644
@@ -263,6 +263,8 @@ characters, each representing a particular tainted value.
12: 'I' if the kernel is working around a severe bug in the platform
firmware (BIOS or similar).
+ 13: 'O' if an externally-built ("out-of-tree") module has been loaded.
The primary reason for the 'Tainted: ' string is to tell kernel
debuggers if this is a clean kernel or if anything unusual has
occurred. Tainting is permanent: even if an offending module is