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] [day] [month] [year] [list]

Message-ID: <20080630083306.GA8283@elte.hu>
Date:	Mon, 30 Jun 2008 10:33:06 +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>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: fix init_memory_mapping over boundary v4


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

> On Sun, Jun 29, 2008 at 12:08 AM, 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
> >>
> >> v2: make init_memory_mapping more solid: start could be any value other than 0
> >> v3: fix NON PAE by handling left over in kernel_physical_mapping
> >> v4: revert back to v2, and use PMD_SHIFT to calculate boundary
> >>     also adjust size for pre-allocated table size
> >
> > i've got v3 applied to tip/master and it worked well in testing - on the
> > old, 512m RAM problem laptop too. So could you send v4 as a delta patch
> > instead please, against tip/master?
> 
> will. before that delta patch please do test on your 512M system .

i've tested it thoroughly on all systems over the weekend and it's all 
fine now. Thanks,

	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/