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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 29 Jun 2007 13:22:31 -0700
From:	Jason Lunz <lunz@...lexsecurity.com>
To:	"Kok\, Auke" <auke-jan.h.kok@...el.com>
Cc:	Mark McLoughlin <markmc@...hat.com>,
	e1000-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
	Jeff Garzik <jeff@...zik.org>
Subject: Re: e1000: backport ich9 support from 7.5.5 ?

On Fri, Jun 29, 2007 at 12:51:02PM -0700, Kok, Auke wrote:
> For distro's not following kernel.org releases we have the perfect 
> solution: A fully tested 7.5.5 driver on sourceforge that was extensively 
> tested against RHEL5 for instance, but also a lot of other older kernels.

I'm sure you and your team have tested the driver thoroughly, but you
cannot hope to match the amount of testing the driver is subjected to by
going into -mm and -rc kernels.

There have been several instances over the years in the e1000 driver
where new releases caused regressions on old or esoteric hardware, and
these were only later discovered by the community. This is why I prefer
kernel.org versions of the e1000 driver, even if they're a little older.

Ordinarily this is a pretty good strategy, because the mainline driver
hasn't usually lagged too far behind new hardware becoming available.
That's no longer true of the newer pcie e1000 parts and the 7.5.5.1
driver.

Is there any specific objection remaining to the merge of e1000 7.5.5.1
into 2.6.23? Is there anything I can do to expedite the process other
than cheer from the sidelines?

Jason
-
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ