linux-kernel - Re: [PATCH] x86: put initial_pg

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: <86802c440903090045y5bfa2201q198c6851c15a1d4d@mail.gmail.com>
Date:	Mon, 9 Mar 2009 00:45:27 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
Subject: Re: [PATCH] x86: put initial_pg_tables into bss -v2

On Sun, Mar 1, 2009 at 4:29 PM, H. Peter Anvin <hpa@...or.com> wrote:
> It's still really ugly, though.  A much easier and cleaner way would seem to
> be to calculate a far limit on the brk and then marking it as a formal
> (non-alloc) section in the linker script and vmlinux file.  That way
> anything that examines the vmlinux file will see it as an exclusion section.
>  We can (and should) even verify that we don't overflow the brk and panic if
> we do.

please check attached patch.

[PATCH] x86: put initial_pg_tables into .bss -v4

Impact: cleanup

Don't use ram after _end blindly for pagetables. aka init pages is before _end
put those pg table into .bss

v2: keep initial page table up to 512M only.
v4: put initial page tables just before _end

Signed-off-by: Yinghai Lu <yinghai@...nel.org>


YH

View attachment "initial_pg_tables_4.patch" of type "text/x-diff" (6433 bytes)