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: Fri, 11 Jan 2008 13:17:16 -0700 From: Matthew Wilcox <matthew@....cx> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Greg KH <gregkh@...e.de>, Arjan van de Ven <arjan@...radead.org>, Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org, Jeff Garzik <jeff@...zik.org>, linux-pci@...ey.karlin.mff.cuni.cz, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Martin Mares <mj@....cz> Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in On Fri, Jan 11, 2008 at 11:58:23AM -0800, Linus Torvalds wrote: > On Fri, 11 Jan 2008, Matthew Wilcox wrote: > > > > So your argument is that MMCONFIG sucks, therefore Linux has to have a > > horrible interface to extended PCI config space? > > What's *your* point? > > MMCONFIG is known broken. If we ever start enabling it more (ie start > using it even if it's not reserved in the e820 tables), all that known > breakage will come and bite us in the *ss. Ivan's patch doesn't start enabling MMCONFIG in more places than we currently do. It makes us use conf1 accesses for all accesses below 256 bytes. That fixes all known problems to date. > We need to have some armor-plated underwear to protect against that > ass-biting, and that's what Arjan's patch is. > > Tell me what *other* armor plating you could have that actually works? The armour plating that already exists -- pci=nommconf. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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