public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Valdis.Kletnieks@vt.edu
Cc: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RFC: virtualbox tainting.
Date: Thu, 6 Oct 2011 13:06:52 -0700	[thread overview]
Message-ID: <20111006200652.GA22225@kroah.com> (raw)
In-Reply-To: <14371.1317930822@turing-police.cc.vt.edu>

On Thu, Oct 06, 2011 at 03:53:42PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 06 Oct 2011 15:50:07 EDT, Dave Jones said:
> 
> > I feel a bit dirty overloading TAINT_CRAP (even if the name is apropos).
> > Should I introduce a TAINT_OUT_OF_TREE perhaps instead ?
> 
> That would fix my biggest issue with the patch - it's a slippery slope.  But if
> we bite the bullet and go straight to the bottom of the slope with an
> OUT_OF_TREE taint, I'd be happy with that.
> 
> Is there a good way to identify at modprobe time if a module is in-tree or
> out-of-tree?

See my previous email, yes, we can do this.

greg k-h

  parent reply	other threads:[~2011-10-06 20:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 19:05 RFC: virtualbox tainting Dave Jones
2011-10-06 19:44 ` Greg KH
2011-10-06 19:50   ` Dave Jones
2011-10-06 19:53     ` Valdis.Kletnieks
2011-10-06 20:03       ` Dave Jones
2011-10-06 20:06       ` Greg KH [this message]
2011-10-06 19:58     ` Greg KH
2011-10-06 20:04       ` Dave Jones
2011-10-06 20:30         ` Greg KH
2011-10-07  8:01         ` Jiri Kosina
2011-10-07 10:02           ` Alan Cox
2011-10-07 16:04           ` Valdis.Kletnieks
2011-10-07 17:01             ` Greg KH
2011-10-07 17:46               ` Dave Jones
2011-10-07  7:03       ` Bastian Blank
2011-10-07 14:40 ` Frank Mehnert
2011-10-07 15:10   ` Dave Jones
2011-10-09 20:12     ` Frank Mehnert
2011-10-07 15:16   ` Josh Boyer
2011-10-07 16:22     ` Valdis.Kletnieks
2011-10-07 18:10       ` Josh Boyer
2011-10-07 18:33         ` Valdis.Kletnieks
2011-10-10  7:58   ` Pekka Enberg
2011-10-10  8:25     ` Dave Airlie
2011-10-10 14:24     ` Greg KH
2011-10-10 16:35       ` Pekka Enberg
2011-10-10 16:49         ` Dave Airlie
2011-10-10 16:51           ` Pekka Enberg
2011-10-10  8:41 ` Maarten Lankhorst
2011-10-10 11:42   ` Josh Boyer
2011-10-12  0:57 ` Parag Warudkar
2011-10-12  7:55   ` Alex Riesen
2011-10-12 14:08     ` Parag Warudkar
2011-10-12 14:18       ` Alex Riesen
2011-10-12 15:00         ` Parag Warudkar
2011-10-12 19:55   ` Zan Lynx
2011-10-12 20:54     ` Parag Warudkar

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=20111006200652.GA22225@kroah.com \
    --to=greg@kroah.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=davej@redhat.com \
    --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