[PATCH] update Doc/oops-tracing.txt for TAINT_USER

[PATCH] update Doc/oops-tracing.txt for TAINT_USER

[Randy Dunlap]

From: Randy Dunlap <randy.dunlap@oracle.com>

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

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 Documentation/oops-tracing.txt |    3 +++
 1 file changed, 3 insertions(+)

--- linux-2.6.20-git9.orig/Documentation/oops-tracing.txt
+++ linux-2.6.20-git9/Documentation/oops-tracing.txt
@@ -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

Re: [PATCH] update Doc/oops-tracing.txt for TAINT_USER

[Theodore Tso]

On Thu, Feb 15, 2007 at 05:04:14PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Add TAINT_USER description to Tainted flags in oops-tracing.txt.
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>  Documentation/oops-tracing.txt |    3 +++
>  1 file changed, 3 insertions(+)
> 
> --- linux-2.6.20-git9.orig/Documentation/oops-tracing.txt
> +++ linux-2.6.20-git9/Documentation/oops-tracing.txt
> @@ -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,

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>


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

Re: [PATCH] update Doc/oops-tracing.txt for TAINT_USER

[Randy Dunlap]

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,
> 
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>


From: Randy Dunlap <randy.dunlap@oracle.com>

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

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---
 Documentation/oops-tracing.txt |    3 +++
 1 file changed, 3 insertions(+)

--- linux-2.6.20-git9.orig/Documentation/oops-tracing.txt
+++ linux-2.6.20-git9/Documentation/oops-tracing.txt
@@ -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