linux-kernel - Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue

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] [day] [month] [year] [list]

Message-ID: <476DB22F.60709@garzik.org>
Date:	Sat, 22 Dec 2007 19:56:15 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Greg KH <gregkh@...e.de>
CC:	Robert Hancock <hancockr@...w.ca>,
	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: [patch] Make MMCONFIG space (extended PCI config space) a driver
 opt-in issue

Greg KH wrote:
> But it is that device, and the driver that controls this device that
> cares about the extended config space.  So it's fair to push this onto
> the driver if needed, instead of forcing the pci core to just blindly
> guess for all devices, and getting it wrong...


Nothing is being forced to guess.  You make sure the broken chipsets 
never enable mmconfig...  just like we do for plenty of other errata.

	Jeff


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