|author||Pavel Emelianov <email@example.com>||2007-07-17 04:03:42 -0700|
|committer||Linus Torvalds <firstname.lastname@example.org>||2007-07-17 10:23:02 -0700|
Report that kernel is tainted if there was an OOPS
If the kernel OOPSed or BUGed then it probably should be considered as tainted. Thus, all subsequent OOPSes and SysRq dumps will report the tainted kernel. This saves a lot of time explaining oddities in the calltraces. Signed-off-by: Pavel Emelianov <email@example.com> Acked-by: Randy Dunlap <firstname.lastname@example.org> Cc: <email@example.com> Signed-off-by: Andrew Morton <firstname.lastname@example.org> [ Added parisc patch from Matthew Wilson -Linus ] Signed-off-by: Linus Torvalds <email@example.com>
Diffstat (limited to 'Documentation/oops-tracing.txt')
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/oops-tracing.txt b/Documentation/oops-tracing.txt
index 23e6dde7eea..7f60dfe642c 100644
@@ -251,6 +251,8 @@ characters, each representing a particular tainted value.
7: 'U' if a user or user application specifically requested that the
Tainted flag be set, ' ' otherwise.
+ 8: 'D' if the kernel has died recently, i.e. there was an OOPS or BUG.
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