From: Randy Dunlap <randy.dunlap@oracle.com>
To: Theodore Tso <tytso@mit.edu>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: Re: [PATCH] update Doc/oops-tracing.txt for TAINT_USER
Date: Fri, 16 Feb 2007 08:30:29 -0800 [thread overview]
Message-ID: <20070216083029.ab6908e4.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070216145033.GA25957@thunk.org>
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
prev parent reply other threads:[~2007-02-16 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 1:04 [PATCH] update Doc/oops-tracing.txt for TAINT_USER Randy Dunlap
2007-02-16 14:50 ` Theodore Tso
2007-02-16 16:30 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070216083029.ab6908e4.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox