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]
Message-ID: <alpine.LFD.0.98.0705231709220.3890@woody.linux-foundation.org>
Date:	Wed, 23 May 2007 17:21:13 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
cc:	Olivier Galibert <galibert@...ox.com>,
	Robert Hancock <hancockr@...w.ca>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Andi Kleen <ak@...e.de>, Chuck Ebbert <cebbert@...hat.com>,
	Len Brown <lenb@...nel.org>
Subject: Re: [RFC PATCH] PCI MMCONFIG: add validation against ACPI motherboard
 resources



On Wed, 23 May 2007, Jesse Barnes wrote:
> 
> After I sent my last message I realized the same thing... though I 
> occasionally hear people talk about removing it (I seriously doubt that 
> will ever happen).  I don't even think there's a way to disable type 1 
> config access on Intel chipsets...

Considering that the chipsets still have support for features that 
*really* aren't used (and haven't been used in over a decade), I doubt the 
conf1 thing is going away any time soon.

Things like: A20 gate, 15-16MB holes, i387 FP exception on irq 13 are 
totally pointless in this day and age. Things like the DMA controller are 
getting there, along with PS/2 keyboard support.

So there's a lot of things that are likely to be removed before conf1 
accesses would. Removing CONF1 accesses would break every single current 
OS, they'll do that ten years from now at the earliest.

			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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ