On Thu, Feb 15, 2007 at 05:04:14PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <[email protected]>
>
> Add TAINT_USER description to Tainted flags in oops-tracing.txt.
>
> Signed-off-by: Randy Dunlap <[email protected]>
> ---
> 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" <[email protected]>
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
