linux-kernel - Re: pci-disable-decode-of-io-memory-during-bar-sizing.patch

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

Date:	Tue, 30 Oct 2007 15:22:19 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
cc:	Arjan van de Ven <arjan@...radead.org>,
	Robert Hancock <hancockr@...w.ca>, Greg KH <greg@...ah.com>,
	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, Jesse Barnes wrote:
>
> The per-device flag is fine with me, but I should make something clear:
> 
> MMCONFIG IS NOT BROKEN!

Trust me, it is.

The particular problem _you_ had with it is only a small small part of the 
bugs we have had.

> What's broken is our PCI probing with certain address space layouts that 
> include MMCONFIG space.

No. You really don't see the big picture. There's been tons of problems 
with MMCONFIG. Like the fact that other devices have their IO regions 
registered on top of it, because the MMCONFIG thing was done as a hidden 
resource. Or the fact that the area claimed was too small. Or too large. 
Or not listed at all.

The whole thing is a total disaster. I told Intel engineers literally 
*years* ago to not do that idiotic "hidden IO resources that are described 
by firmware that then inevitably gets things wrong", and yet what happens? 
Every single time.

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