linux-kernel - Re: RFC: virtualbox tainting.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111010142418.GC21944@kroah.com>
Date:	Mon, 10 Oct 2011 07:24:18 -0700
From:	Greg KH <greg@...ah.com>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Frank Mehnert <frank.mehnert@...cle.com>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andy Hall <andy.hall@...cle.com>
Subject: Re: RFC: virtualbox tainting.

On Mon, Oct 10, 2011 at 10:58:48AM +0300, Pekka Enberg wrote:
> Hi Frank,
> 
> On Fri, Oct 7, 2011 at 5:40 PM, Frank Mehnert <frank.mehnert@...cle.com> wrote:
> > 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. 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.
> 
> What is holding you back from submitting the vbox modules to kernel
> staging tree and starting to clean it up for proper inclusion?

You haven't actually read the vbox kernel code before, have you :)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/