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]

Date:	Wed, 12 Oct 2011 10:08:15 -0400
From:	Parag Warudkar <parag.lkml@...il.com>
To:	Alex Riesen <raa.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 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
opt out based on the fact that it cannot find enough info in the OOPS
- missing module list for example. But I don't think that's a very
likely scenario - oops is in most cases accompanied by tainted flag
and module list - the possibility of OOPS printing only tainted but
not module list is not very real and can be ignored.

Parag
--
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/