From: "Robert P. J. Day" <rpjday@mindspring.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: what is the rationale for "TAINT_USER"?
Date: Fri, 12 Oct 2007 08:37:04 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0710120832350.22555@localhost.localdomain> (raw)
In-Reply-To: <20071012122719.GB30350@atjola.homenet>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1225 bytes --]
On Fri, 12 Oct 2007, Björn Steinbrink wrote:
> On 2007.10.12 08:04:20 -0400, Robert P. J. Day wrote:
> >
> > i can see what the theoretical purpose for it is here:
> >
> > http://kerneltrap.org/node/6656
> >
> > but it's not clear how it can possibly be set from userland given
> > that:
> >
> > $ grep -r TAINT_USER *
> > include/linux/kernel.h:#define TAINT_USER (1<<6)
> > kernel/panic.c: tainted & TAINT_USER ? 'U' : ' ',
> > $
> >
> > am i missing something screamingly obvious?
>
> Grepping for "tainted" leads me to:
>
> echo 32 > /proc/sys/kernel/tainted
???. i have no idea what you were grepping through to find that
phrase, but TAINT_USER would seem to be equivalent to echo 64, not
echo 32, anyway, no?
in any event, as i posted in a followup, i'm assuming that that
particular bit is meant to be set explicitly from user space using
something like:
# echo 64 > /proc/sys/kernel/tainted
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next prev parent reply other threads:[~2007-10-12 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 12:04 Robert P. J. Day
2007-10-12 12:18 ` Robert P. J. Day
2007-10-12 12:27 ` Björn Steinbrink
2007-10-12 12:37 ` Robert P. J. Day [this message]
2007-10-12 12:48 ` Björn Steinbrink
2007-10-12 12:30 ` Nadia Derbey
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=Pine.LNX.4.64.0710120832350.22555@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=B.Steinbrink@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®