public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Theodore Tso <tytso@mit.edu>, Greg KH <greg@kroah.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add user taint flag
Date: Wed, 24 May 2006 10:15:12 -0400	[thread overview]
Message-ID: <20060524141512.GF28702@redhat.com> (raw)
In-Reply-To: <20060524135533.GD28702@redhat.com>

On Wed, May 24, 2006 at 09:55:33AM -0400, Dave Jones wrote:
 > On Wed, May 24, 2006 at 09:39:16AM -0400, Theodore Tso wrote:
 >  > On Tue, May 23, 2006 at 11:45:06AM -0700, Greg KH wrote:
 >  > > On Sun, May 21, 2006 at 07:04:32PM -0400, Theodore Ts'o wrote:
 >  > > > --- linux-2.6.orig/kernel/panic.c	2006-04-28 21:16:55.000000000 -0400
 >  > > > +++ linux-2.6/kernel/panic.c	2006-05-21 19:00:15.000000000 -0400
 >  > > > @@ -150,6 +150,7 @@
 >  > > >   *  'R' - User forced a module unload.
 >  > > >   *  'M' - Machine had a machine check experience.
 >  > > >   *  'B' - System has hit bad_page.
 >  > > > + *  'U' - Userspace-defined naughtiness.
 >  > > 
 >  > > Just a note, some other distros already use the 'U' flag in taint
 >  > > messages to show an "unsupported" module has been loaded.  I know it's
 >  > > out-of-the-tree and will never go into mainline, just FYI if you happen
 >  > > to see some 'U' flags in the wild today...
 >  > > 
 >  > > Oh, and I like this feature, makes sense to me to have this.
 >  > 
 >  > Should we worry about collisions with what distributions are using?
 >  > That could cause confusion in the future....
 > 
 > We use it in Fedora/RHEL if a module is loaded that hasn't been gpg signed.
 > It's been handy to spot things like 3rd parties replacing jbd.ko with
 > their own variant in bug-reports.

Brainfart on my part. We mark such modules as (U) in the module list in oopses,
but we don't actually taint.

Meh, too early for davej's.

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2006-05-24 14:15 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
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 [this message]
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=20060524141512.GF28702@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --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