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: <86802c440806280001j6184240v49c1a329896d8d45@mail.gmail.com>
Date:	Sat, 28 Jun 2008 00:01:06 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
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

On Fri, Jun 27, 2008 at 11:35 PM, 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.
>
>> v2: make init_memory_mapping more solid: start could be any value
>> other than 0
>
> very good idea!

could change
map_pfn_mapped = init_memory_mapping(0, map_low_pfn<<PAGE_SHIFT);
to
map_pfn_mapped = init_memory_mapping(map_pfn_mapped<<PAGE_SHIFT,
map_low_pfn<<PAGE_SHIFT);

only concern is
init_memory_mapping set   _EXEC in page table for kernel code.

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