linux-kernel - Re: Oops report for the week preceding June 16th, 2008

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: <20080617092023.GA20621@elte.hu>
Date:	Tue, 17 Jun 2008 11:20:23 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"John W. Linville" <linville@...driver.com>,
	Dave Jones <davej@...hat.com>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: Oops report for the week preceding June 16th, 2008

* Arjan van de Ven <arjan@...ux.intel.com> wrote:

> This week, a total of 3877 oopses and warnings have been reported, 
> compared to 3390 reports in the previous week.
>
> Recently, Fedora put out an updated kernel that contained a wireless 
> update; unfortunately, this update was rather broken and caused 
> various things to show up in the top 20. A few days later, another 
> update fixing the most obvious ones got released with the result that 
> only rank 2 and 9 are from the broken update, rather than a lot more..

sidenote: i suspect Fedora has done this to enable more hardware, and/or 
to fix mainline wireless bugs?

I wish we would do such new driver merging in mainline instead, so that 
we had a single point of testing and single point of effort.

Same for Nouveau: Fedora carries it and i dont understand why such a 
major piece of work is not done in mainline and not _helped by_ 
mainline. It's not like there would be any big risk from having such a 
new, experimental 3D driver around - instead of people running nvidia.ko 
that causes trouble in all sorts of other subsystems.

All the years of moaning about nvidia.ko and finally we have some real 
OSS project and real chance of action but after a year of development 
Nouveau still has not been picked up ...

When distros feel the need to add large and risky patches that IMO shows 
process failure on our part and further isolates mainline from distros 
and from testers.

While we dont want to merge anything that gets thrown at us, not merging 
new, major, new-hardware-enabling OSS drivers in the mainline kernel is 
almost the same thing as intentionally hurting OSS projects and helping 
binary-only drivers.

	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/