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
| ||
|
Date: Mon, 26 May 2008 11:36:09 +0200 From: Ingo Molnar <mingo@...e.hu> To: Arjan van de Ven <arjan@...ux.intel.com> Cc: Chris Wright <chrisw@...s-sol.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Greg KH <greg@...ah.com>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: Top 10 bugs/warnings for the week of March 23rd, 2008 * Arjan van de Ven <arjan@...ux.intel.com> wrote: >> At any rate, they have a bug in their proprietary module (news at >> 11). >> >> So, I don't think this should make the top ten. Do you have a way to >> sort tainted vs non-tainted, and only produce the top ten for >> untainted? > > yes absolutely; this is a question I'll have for the customers of the > data... do people want to see "only-tainted" in these top 10s? Right > now I mark them as such but leave them in. It's trivial for me to just > leave them out instead (the info is there, just a matter of not > counting) i think they should be included, but perhaps abbreviated [into 1-2 lines] so that they do not hold us up. We must not whitewash our bug statistics by intentionally excluding the harm that bin-only modules do to our users - but we can make them less visually intrusive, so that we can work on fixing the bugs we can fix. Perhaps make sure it's top 10 of _our_ bugs, with the bin-only data mixed in as well (in a visually unintrusive way) to make the picture complete. I.e. list 20 bugs if 10 of them are bin-only modules. Ingo -- 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/
Powered by blists - more mailing lists