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: <CALxABCYQP52grqBr_8163baGuMDGPe7uL4f5Xa2-dr6MhsQ_Ow@mail.gmail.com>
Date:	Wed, 12 Oct 2011 16:18:09 +0200
From:	Alex Riesen <raa.lkml@...il.com>
To:	Parag Warudkar <parag.lkml@...il.com>
Cc:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: RFC: virtualbox tainting.

On Wed, Oct 12, 2011 at 16:08, Parag Warudkar <parag.lkml@...il.com> wrote:
> On Wed, Oct 12, 2011 at 3:55 AM, Alex Riesen <raa.lkml@...il.com> wrote:
>> On Wed, Oct 12, 2011 at 02:57, Parag Warudkar <parag.lkml@...il.com> wrote:
>>> Why can't the automatic bug filing tools have a user space list of
>>> offending modules that it can use to opt out of automatically filing
>>> kernel bugs? ...
>>
>> Maybe because an oops is not always conveniently accompanied by enough
>> information
>> to opt-out.
>>
>
> In which case the reporting of the OOPS is useless anyways
> irrespective of whether or not vboxdrv was loaded. So the tool  can

Of course not. There is a lot of insight in the instruction dump,
which may be still present, or in stack trace.
--
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/