| 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
| ||
|
Message-ID: <4BBFADDB.6000508@zytor.com> Date: Fri, 09 Apr 2010 15:44:43 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Andy Isaacson <adi@...apodia.org> CC: Yinghai Lu <yinghai.lu@...cle.com>, guenter.roeck@...csson.com, Linus Torvalds <torvalds@...ux-foundation.org>, Bjorn Helgaas <bjorn.helgaas@...com>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, "x86@...nel.org" <x86@...nel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Thomas Renninger <trenn@...e.de> Subject: Re: [PATCH] x86: Reserve legacy VGA MMIO area for x86_64 as well as x86_32 On 04/09/2010 03:35 PM, Andy Isaacson wrote: > [ 2.267740] pci 0000:00:1f.2: BAR 5: assigned [mem 0x000a0000-0x000a07ff] > [ 2.274701] pci 0000:00:1f.2: BAR 5: set to [mem 0x000a0000-0x000a07ff] (PCI address [0xa0000-0xa07ff] Looks like this is something the kernel is assigning to it. It *does* get marked reserved: > [ 0.000000] #6 [000009ec00 - 00000f0000] BIOS reserved ... but that doesn't seem to keep the PCI code from assigning anything there. This is a Very Bad thing in general... if we're assigning devices to areas marked reserved, we have a huge problem. -hpa -- 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