Skip to contentSkip to conversation

update Doc/oops-tracing.txt for TAINT_USER

PATCH In review Randy Dunlap 2 participants 3 messages Feb 16, 2007 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 update Doc/oops-tracing.txt for TAINT_USER

From: Randy Dunlap <[email protected]>

Add TAINT_USER description to Tainted flags in oops-tracing.txt.

---
 Documentation/oops-tracing.txt |    3 +++
 1 file changed, 3 insertions(+)
Documentation/oops-tracing.txt +3 -0
@@ -234,6 +234,9 @@ characters, each representing a particul
   6: 'B' if a page-release function has found a bad page reference or
      some unexpected page flags.
 
+  7: 'U' if a user specifically requested that the Tainted flag be set,
+     ' ' otherwise.
+
 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
#1 lore raw
Quoted 12 lines · Randy Dunlap

From: Randy Dunlap <[email protected]>

Add TAINT_USER description to Tainted flags in oops-tracing.txt.

---
 Documentation/oops-tracing.txt |    3 +++
 1 file changed, 3 insertions(+)

Documentation/oops-tracing.txt characters, each representing a particul · line 239

Quoted 6 lines
Documentation/oops-tracing.txt +3 -0
@@ -234,6 +234,9 @@ characters, each representing a particul
   6: 'B' if a page-release function has found a bad page reference or
      some unexpected page flags.
 
+  7: 'U' if a user specifically requested that the Tainted flag be set,
+     ' ' otherwise.
+

I suggest you change this to read "if a user or user application".

Otherwise,

BTW, most often it will be a specific user application. The initial intended use case was a Java Virtual Machine, that will set the Tainted flag as a hint to support personnel that Java program it was running was doing something really evil and non-portable (direct access to physical memory) which unfortunately the RTSJ compliance test requires us to support . Thank you very much, Sun....

"Java: Write once, run screaming". :-)

- Ted

#2 lore raw
Quoted 5 lines · On Fri, 16 Feb 2007 09:50:33 -0500 Theodore Tso wrote:

I suggest you change this to read "if a user or user application".

Otherwise,

From: Randy Dunlap <[email protected]>

Add TAINT_USER description to Tainted flags in oops-tracing.txt.

---
 Documentation/oops-tracing.txt |    3 +++
 1 file changed, 3 insertions(+)
Documentation/oops-tracing.txt +3 -0
@@ -234,6 +234,9 @@ characters, each representing a particul
   6: 'B' if a page-release function has found a bad page reference or
      some unexpected page flags.
 
+  7: 'U' if a user or user application specifically requested that the
+     Tainted flag be set, ' ' otherwise.
+
 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