linux-kernel - Re: [PATCH] x86: fix init_memory

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: <20080628070243.GA31342@elte.hu>
Date:	Sat, 28 Jun 2008 09:02:43 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: fix init_memory_mapping over boundary v2


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

> * Yinghai Lu <yhlu.kernel@...il.com> wrote:
> 
> > some end boundary is only page alignment, instead of 2M alignment, so 
> > call ker_phycial_mapping_init three times. then don't overmap above 
> > the max_low_pfn
> 
> applied to tip/x86/unify-setup, thanks Yinghai.

-tip testing found a 32-bit spontaneous reboot during bootup, with this 
config:

  http://redhat.com/~mingo/misc/config-Sat_Jun_28_08_43_52_CEST_2008.bad

no serial log produced at all.

doing the reverts below fixes the problem.

	Ingo

commit 4ae56755fa1e1bd1500c97b5bf82d6519a261ffd
Author: Ingo Molnar <mingo@...e.hu>
Date:   Sat Jun 28 08:59:44 2008 +0200

    Revert "x86: let setup_arch call init_apic_mappings for 32bit"

    This reverts commit 7fce3bb20100e5b6c42ad66c495e6348522bfd37.

commit 2703b959fc588f1b77290272f60bcf0bd8f6e557
Author: Ingo Molnar <mingo@...e.hu>
Date:   Sat Jun 28 08:59:39 2008 +0200

    Revert "x86: fix init_memory_mapping over boundary v2"

    This reverts commit 7a41ed2c98f860da38a944d8de5b29e6ec39cf76.

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