netdev - 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: <m363uqwpds.fsf@maximus.localdomain>
Date:	Thu, 10 Apr 2008 01:59:59 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Frans Pop <elendil@...net.nl>
Cc:	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, torvalds@...ux-foundation.org,
	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)

Frans Pop <elendil@...net.nl> writes:

> Fairly experienced user wants a kernel which supports his hardware without 
> having to load modules, but wants other modules available "just in case".
> So he takes his distro kernel and selectively changes some modules to 
> built-ins, including e1000.
> Next he upgrades to 2.6.25 and finds his NIC no longer works.

Nope, udev with normal distro config will load e1000e just fine.
A custom system, without automatic loading of modules (or with
unavailable module) could have this problem. A root fs on NFS or
something like that, too.

But while it can be changed for 2.6.25 it will break with 2.6.26 again,
definitely.
-- 
Krzysztof Halasa
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html