linux-kernel - Re: [patch] e1000=y && e1000e=m regression fix

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, 9 Apr 2008 22:04:33 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Matthew Wilcox <matthew@....cx>,
	"Kok, Auke" <auke-jan.h.kok@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	NetDev <netdev@...r.kernel.org>,
	e1000-list <e1000-devel@...ts.sourceforge.net>,
	linux-pci maillist <linux-pci@...ey.karlin.mff.cuni.cz>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"David S. Miller" <davem@...emloft.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	"Ronciak, John" <john.ronciak@...el.com>,
	"Allan, Bruce W" <bruce.w.allan@...el.com>,
	Greg KH <greg@...ah.com>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [patch] e1000=y && e1000e=m regression fix


* Jeff Garzik <jeff@...zik.org> wrote:

> Ingo Molnar wrote:
>> * Jeff Garzik <jeff@...zik.org> wrote:
>>
>>>> We've got three thousand Kconfig options - it is clearly not realistic 
>>>> for users to keep such details in mind to avoid pitfalls.
>>> Agreed -- hence the multiple announcements, including in this thread, to 
>>> put said details into mind.
>>
>> which part of "it took a kernel developer more than an hour to figure 
>> out why his laptop had a dead network interface" did you not 
>> understand? Whatever you did, it was not apparent to me. I dont 
>> follow every tiny detail of the e1000 driver family, nor do 99%+ [*] 
>> of our users.
>
> You do follow LKML, where multiple announcements have and are being 
> posted.

... what you say is contrary to the well-known regression rules of the 
upstream kernel. You cannot seriously expect users to follow mailings 
related to the 8+ million lines of code kernel they are utilizing, just 
to not end up with a dead networking interface ....

so please comment on the fix i sent. The patch solves the problem i had 
and it's end of this story as far as i'm concerned. Do you have any 
strong technical argument why it should not be applied?

	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/