mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 19:21:31 -04:00
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 protected]> Acked-by: Randy Dunlap <[email protected]> Cc: <[email protected]> Signed-off-by: Andrew Morton <[email protected]> [ Added parisc patch from Matthew Wilson -Linus ] Signed-off-by: Linus Torvalds <[email protected]>
This commit is contained in:
parent
74489a91dd
commit
bcdcd8e725
21 changed files with 24 additions and 2 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in a new issue