All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RFC: virtualbox tainting.
Date: Thu, 6 Oct 2011 15:50:07 -0400	[thread overview]
Message-ID: <20111006195007.GA24900@redhat.com> (raw)
In-Reply-To: <20111006194432.GA21642@kroah.com>

On Thu, Oct 06, 2011 at 12:44:32PM -0700, Greg Kroah-Hartman wrote:
 
 > > diff --git a/kernel/module.c b/kernel/module.c
 > > index 04379f92..d26c9a3 100644
 > > --- a/kernel/module.c
 > > +++ b/kernel/module.c
 > > @@ -2653,6 +2653,10 @@ static int check_module_license_and_versions(struct module *mod)
 > >  	if (strcmp(mod->name, "ndiswrapper") == 0)
 > >  		add_taint(TAINT_PROPRIETARY_MODULE);
 > >  
 > > +	/* vbox is garbage. */
 > > +	if (strcmp(mod->name, "vboxdrv") == 0)
 > > +		add_taint(TAINT_CRAP);
 > 
 > Odds are we should have a list of these types of modules, as I think
 > there are a few others out there we should mark this way :)

possibly, though this is by far the leader (for us at least) today.

 > But anyway, I like this, and I think I'll go add it to the openSUSE
 > kernels so we can avoid the numerous bug reports we get there as well
 > for this crappy driver.
 > 
 > 	Acked-by: Greg Kroah-Hartman <gregkh@suse.de>

I feel a bit dirty overloading TAINT_CRAP (even if the name is apropos).
Should I introduce a TAINT_OUT_OF_TREE perhaps instead ?

	Dave


  reply	other threads:[~2011-10-06 19:50 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 [this message]
2011-10-06 19:53     ` Valdis.Kletnieks
2011-10-06 20:03       ` Dave Jones
2011-10-06 20:06       ` Greg KH
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=20111006195007.GA24900@redhat.com \
    --to=davej@redhat.com \
    --cc=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.