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:	Mon, 29 Nov 2010 18:36:20 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	"H. Peter Anvin" <hpa@...or.com>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] x86/PCI: never allocate PCI space from the last 1M
	below 4G

On Mon, Nov 29, 2010 at 11:30:09AM -0700, Bjorn Helgaas wrote:
> 
> The last 1M before 4G contains the processor restart vector and usually
> the system ROM.  We don't know the actual ROM size; I chose 1M because
> that's how much Windows 7 appears to avoid.
> 
> Without this check, we can allocate PCI space that will never work.  On
> Matthew's HP 2530p, we put the Intel GTT "Flush Page" at the very last
> page, which causes a spontaneous power-off:
> 
>   pci_root PNP0A08:00: host bridge window [mem 0xfee01000-0xffffffff]
>   fffff000-ffffffff : Intel Flush Page (assigned by intel-gtt)
> 
> Reference: https://bugzilla.kernel.org/show_bug.cgi?id=23542
> Reported-by: Matthew Garrett <mjg@...hat.com>
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@...com>

Tested-by: Matthew Garrett <mjg@...hat.com>

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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