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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20080628074753.GA1856@elte.hu>
Date:	Sat, 28 Jun 2008 09:47:53 +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


* Yinghai Lu <yhlu.kernel@...il.com> wrote:

> On Sat, Jun 28, 2008 at 12:02 AM, Ingo Molnar <mingo@...e.hu> wrote:
> >
> > * 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.
> even with console=uart8250,io,0x03f8,115200n8 ?

correct, i use earlyprintk=serial,ttyS0,115200.

i just re-tested it - doing "git merge tip/x86/unify-setup" in the 
tip/master branch triggers the failure with that config on a wide range 
of 32-bit boxes.

	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/