linux-kernel - Re: [PATCH] [9/50] i386: validate against ACPI motherboard resources

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: <46F542A4.9080207@shaw.ca>
Date:	Sat, 22 Sep 2007 10:28:20 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	Andi Kleen <ak@...e.de>, rajesh.shah@...el.com,
	jbarnes@...tuousgeek.org, greg@...ah.com, patches@...-64.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [9/50] i386: validate against ACPI motherboard resources

Yinghai Lu wrote:
> No!
> 
> MMCONFIG will not work with acpi=off any more.

I don't think this is unreasonable. The ACPI MCFG table is how we are 
supposed to learn about the area in the first place. If we can't get the 
table location via an approved mechanism, and can't validate it doesn't 
overlap with another memory reservation or something, I really don't 
think we should be using it.

I don't think it's much of an issue anyway - the chances that somebody 
will want to run without ACPI on a system with MCFG are pretty low given 
that you'll end up losing a bunch of functionality (not least of which 
is multi-cores).

> 
> because acpi_init==>pci_mmcfg_late_init==>pci_mmcfg_check_hostbridge...
> 
> can you move pci_mmcfg_later_init out of acpi_init and just call
> somewhere after acpi_init...
> or put pci_mmcfg_check_hostbridge back to pci_mmcfg_early_init?
> 
> YH
> 
-
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/