From: Stefan Seyfried <seife@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
Holger Macht <hmacht@suse.de>
Subject: Re: [PATCH] Add user taint flag
Date: Wed, 24 May 2006 15:43:38 +0200 [thread overview]
Message-ID: <20060524134338.GB20628@suse.de> (raw)
In-Reply-To: <20060522033644.26d47a00.akpm@osdl.org>
On Mon, May 22, 2006 at 03:36:44AM -0700, Andrew Morton wrote:
> "Theodore Ts'o" <tytso@mit.edu> wrote:
> >
> > Allow taint flags to be set from userspace by writing to
> > /proc/sys/kernel/tainted, and add a new taint flag, TAINT_USER, to be
> > used when userspace is potentially doing something naughty that might
> > compromise the kernel.
>
> What sort of userspace actions are you thinking of here?
I also thought about tainting the kernel from a userspace program that
messes with runtime power management - switch off and on various devices
at runtime (which is not recommended by anyone) - and you are clearly in
Unsupportedland.
So yes, this is a good idea (although i just would have written a module
without MODULE_LICENSE that just printk'ed "Tainting kernel, we will use
runtime power management" on load.)
--
Stefan Seyfried \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, Nürnberg \ -- Leonard Cohen
next prev parent reply other threads:[~2006-05-24 13:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 23:04 [PATCH] Add user taint flag Theodore Ts'o
2006-05-22 10:36 ` Andrew Morton
2006-05-22 18:33 ` Theodore Tso
2006-05-22 23:49 ` Nick Piggin
2006-05-24 13:43 ` Stefan Seyfried [this message]
2006-05-22 12:17 ` Stephen C. Tweedie
2006-05-22 14:14 ` Arjan van de Ven
2006-05-22 14:35 ` Alan Cox
2006-05-22 14:29 ` Valdis.Kletnieks
2006-05-22 18:56 ` Jan Engelhardt
2006-05-22 14:37 ` Arjan van de Ven
2006-05-23 1:11 ` Theodore Tso
2006-05-22 15:48 ` Randy.Dunlap
2006-05-23 18:45 ` Greg KH
2006-05-24 13:39 ` Theodore Tso
2006-05-24 13:55 ` Dave Jones
2006-05-24 14:15 ` Dave Jones
2006-05-25 15:01 ` Greg KH
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=20060524134338.GB20628@suse.de \
--to=seife@suse.de \
--cc=akpm@osdl.org \
--cc=hmacht@suse.de \
--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