linux-kernel - Re: [crash] Re: Latest brk patchset

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: <49BE97D5.4010002@zytor.com>
Date:	Mon, 16 Mar 2009 11:17:57 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Yinghai Lu <yinghai@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [crash] Re: Latest brk patchset

Jeremy Fitzhardinge wrote:
> Yinghai Lu wrote:
>> could be max_pfn_mapped change in head_32.S that reduce mapping range 
>> to _end only.
>>   
> 
> Yes, I would say you're right.  Trimming the mapping to _end only leaves 
> the space under the kernel avaliable for allocating pagetable from e820 
> space.  In this case we've got DEBUG_PAGEALLOC enabled, which inhibits 
> the use of PSE, and BIOS corruption checking on, which eats a chunk of 
> low memory.  In combination, there's only 0x8f000 bytes free below the 
> kernel, and it needs 0xe1000 to allocate for pagetables.
> 
> Reverting 2bd2753ff46346543ab92e80df9d96366e21baa5 fixes the problem for 
> me, though it does result in a kernel with a 73MB BSS...
> 

Waitaminute... there is no way we could end up with 73 MB page tables 
unless something is seriously screwy.  Even with PAE and !PSE, we only 
get 2 MB worth of page tables for each 1 GB mapped -- even with a 4:4 
scheme this is only 8 MB.

	-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/