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

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: <alpine.LFD.1.00.0804100724220.3143@woody.linux-foundation.org>
Date:	Thu, 10 Apr 2008 07:30:34 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Krzysztof Halasa <khc@...waw.pl>
cc:	Frans Pop <elendil@...net.nl>, Ingo Molnar <mingo@...e.hu>,
	jeff@...zik.org, matthew@....cx, auke-jan.h.kok@...el.com,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	e1000-devel@...ts.sourceforge.net,
	linux-pci@...ey.karlin.mff.cuni.cz, akpm@...ux-foundation.org,
	davem@...emloft.net, jesse.brandeburg@...el.com,
	john.ronciak@...el.com, bruce.w.allan@...el.com, greg@...ah.com,
	arjan@...ux.intel.com, rjw@...k.pl
Subject: Re: [patch] e1000=y && e1000e=m regression fix (was: Re: [regression]
 e1000e broke e1000)

On Thu, 10 Apr 2008, Krzysztof Halasa wrote:
> >
> > Not for us that don't compile modules at all, or only modules for the 
> > devices we actually have.
> 
> That would work, too.

No it wouldn't, not when the driver we used forever suddenly stopped 
supporting them.

The fact that some *other* driver that I'd never ever enabled in my life 
suddenly supports them is irrelevant - it's not in my list of "hardware I 
have", and it's not even getting compiled.

And no, I'm not talking about some theoretical "this could happen" thing. 
I hit exactly that with commit 040babf9d84e7010c457e9ce69e9eb1c27927c9e (I 
then thought that the new driver didn't even work for me, but that turned 
out to be an unrelated bug).

It's very irritating when a working machine suddenly just stops working 
because some config option just changed its meaning. VERY irritating.

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