| 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
| ||
|
Date: Sat, 1 Sep 2007 12:18:16 +0200 From: Andi Kleen <ak@...e.de> To: Matthew Wilcox <matthew@....cx> Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>, alex@...bles.it, dac@...glom-o.org, "bugme-daemon@...nel-bugs.osdl.org" <bugme-daemon@...zilla.kernel.org>, linux-scsi@...r.kernel.org Subject: Re: [Bug 8942] dac960 driver stopped working with 2.6.22 kernel series > So anyway, what's actually failing is one of these: Thanks for the analysis. In theory we could not fail DAC if the machine has <4GB RAM to work around such buggy drivers, but then they would fail anyways with >4GB. Also the failure was intended to allow some drivers to use more efficient non DAC operation. > It seems a bit mean to write off *all* VIA bridges as data-corruptors. > Maybe the people who haven't had problems before can help us start a > white-list of VIA PCI bridges that don't have a problem with DAC. The reason I blacklisted all was that there was a small triple of data corruption reports with VIA bridges. Also it's impossible to get any errata information out of VIA. And there are not that many >4GB VIA systems because these chipsets are usually used in lower end systems. -Andi - 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/
Powered by blists - more mailing lists