From: Dave Jones <davej@redhat.com>
To: Frank Mehnert <frank.mehnert@oracle.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andy Hall <andy.hall@oracle.com>
Subject: Re: RFC: virtualbox tainting.
Date: Fri, 7 Oct 2011 11:10:04 -0400 [thread overview]
Message-ID: <20111007151003.GA26358@redhat.com> (raw)
In-Reply-To: <201110071640.53827.frank.mehnert@oracle.com>
On Fri, Oct 07, 2011 at 04:40:53PM +0200, Frank Mehnert wrote:
> I can understand that you would rather ignore bug reports from external
> kernel modules. On the other hand I don't like the TAINT_CRAP flag as
> you can probably imagine.
>
> Why not just mark external modules like Bastian Blank suggested? I can
> assure that we will not try circumvent a TAINT_OOT_MODULE flag.
Sure. The exact mechanism used doesn't matter to me.
> Please also note that we always have good relations to the open source
> community so feel free to point me an archive where all these kernel
> panic reports arrive which you've got.
Search through the fedora kernel bugs at bugzilla.redhat.com for 'vboxdrv'
or 'virtual box' (note to search for closed bugs as well as open ones).
> We fixed some bugs in our kernel
> modules in the past and it is even possible that some of the current
> bug reports are from older versions of VirtualBox which might have been
> fixed in the meantime.
>
> And of course, helpful and constructive critism is always appreciated.
If you'd like to be cc'd on those reports, I can add you to the bugs
when we go through them if you create a bugzilla account.
Dave
next prev parent reply other threads:[~2011-10-07 15:10 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
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 [this message]
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=20111007151003.GA26358@redhat.com \
--to=davej@redhat.com \
--cc=andy.hall@oracle.com \
--cc=frank.mehnert@oracle.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