| 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: Tue, 30 Oct 2007 16:52:02 -0700 From: Arjan van de Ven <arjan@...radead.org> To: Robert Hancock <hancockr@...w.ca> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Greg KH <greg@...ah.com>, Jesse Barnes <jbarnes@...tuousgeek.org>, akpm@...ux-foundation.org, ak@...e.de, rajesh.shah@...el.com, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch On Tue, 30 Oct 2007 17:41:26 -0600 Robert Hancock <hancockr@...w.ca> wrote: > > I could easily see device driver writers probing to see if > > something works, and I absolutely don't think we should just > > automatically enable MMCONFIG from then on. > > Why per device? It's not like the MSI case where both the platform > and the device are potentially busted. Whether or not MMCONFIG works > has nothing to do with the device, all that matters is whether it > works on the platform. It shouldn't be the driver's responsibility to > know this. it's per device so that if you have have no users for this stuff, you'll never ever get bitten by bugs (be it linux or the bios). It's just avoiding the problem for a large class of cases... doesn't mean it's solved for the other class, just in practice it turns it into a much smaller problem. - 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