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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090315204206.GA16184@elte.hu>
Date:	Sun, 15 Mar 2009 21:42:06 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [crash] Re: Latest brk patchset


* Ingo Molnar <mingo@...e.hu> wrote:

> the previous kit in tip:x86/setup-memory is causing crashes. 
> One of them is:
> 
> init_memory_mapping: 0000000000000000-00000000377fe000                              
>  0000000000 - 00377fe000 page 4k                                                    
> Kernel panic - not syncing: Cannot find space for the kernel 

excluding these commits from tip:master:

2bd2753: x86: put initial_pg_tables into .bss
796216a: x86: allow extend_brk users to reserve brk space
7543c1d: x86-32: compute initial mapping size more accurately
6de6cb4: x86: use brk allocation for DMI
ccf3fe0: x86-32: use brk segment for allocating initial kernel pagetable
5368a2b: x86: move brk initialization out of #ifdef CONFIG_BLK_DEV_INITRD
93dbda7: x86: add brk allocation for very, very early allocations
b9719a4: x86: make section delimiter symbols part of their section

fixes the crashes.

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