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  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]
Date:	Sun, 01 Mar 2009 01:20:22 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yinghai@...nel.org>
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

Yinghai Lu wrote:
> Impact: cleanup
> 
> Don't use ram after _end blindly for pagetables.
> put those pg table into bss
> 
> also remove init_pg_tables_start/end tricks all around
> 
> v2: keep initial page table up to 512M only.
> 

I really, REALLY, don't like this.  This is going right back to the 
situation which we had before the dynamically generated page tables.  We 
now have yet another hardcoded limit, and big chunk of wasted memory in 
case we don't need to allocate it all.

   * Modulo rounding, each megabyte assigned here requires a kilobyte of
   * memory, which is currently unreclaimed.

You're potentially throwing away half a megabyte, which is a major deal 
on a small embedded system!

No, this is garbage.  If you're insisting on getting rid of the brk-like 
allocation patterns, then you have to get an alternative dynamic 
allocator available to the pre-paging code.  Now, there is no reason we 
couldn't execute C code before enabling paging, although the code would 
either have to be PIC or linked at the physical address.

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

Powered by blists - more mailing lists