| 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: <1213986352.31598.16.camel@promb-2n-dhcp368.eng.vmware.com> Date: Fri, 20 Jun 2008 11:25:52 -0700 From: Alok Kataria <akataria@...are.com> To: Ingo Molnar <mingo@...e.hu> Cc: Andrew Morton <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, yhlu.kernel@...il.com Subject: Re: Is e820_setup_gap broken ?? On Fri, 2008-06-20 at 11:14 -0700, Alok Kataria wrote: > I am looking at the e820_setup_gap function in tip/master tree. > > For i386 if we don't find a big enough gap in e820 map, we keep the > gapstart value to "0x10000000". Don't print any warning messages for the > user that we were unable to find gap in the 32bit address range. > > Now this address 0x10000000 can actually be used by the system ram or > may have been reserved for some reason. Wouldn't the system break if the > PCI devices started using this gap in such a case ? Ok I take this back. In the PCI code path when we actually use this gap start address for allocating the resource...allocate_resource will shout about the memory address being already in use. And the pci device won't be allocated which is the right thing to do. > Also note that this is not just a problem with the tip/master tree in > the current mainline tree too we do similar stuff for i386 kernel. > > Thanks, > Alok -- 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