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: <CAE9FiQX4nQ7_1kg5RL_vh56rmcSHXUi1ExrZX7CwED4NGMnHfg@mail.gmail.com>
Date:	Wed, 6 Mar 2013 14:44:01 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...ux.intel.com>
Cc:	Henrik Rydberg <rydberg@...omail.se>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.9-rc1

On Wed, Mar 6, 2013 at 2:27 PM, H. Peter Anvin <hpa@...ux.intel.com> wrote:
> On 03/06/2013 02:04 PM, Henrik Rydberg wrote:
>>>
>>> Sigh.  This is why "keep the page tables together" is fundamentally the
>>> wrong strategy.
>>>
>>> 8M means that we won't even be able to boot on machines with less than
>>> 16M or so of RAM... I'm not sure if anyone still cares, but that is a
>>> pretty aggressive heuristic.
>>
>> Maybe this should be a config option, given the ad-hoc nature of the
>> chosen value? Anyway, the patch works.
>>
>
> Can we make a sensible argument for what the value *needs* to be?  2M at
> least makes a modicum of sense.  Either way, it's clear we still have
> plenty of cleaning up to do...

ok, let's stay with 2M.

Please check attached v1 with updated commit log.

Thanks

Yinghai

Download attachment "fix_real_end_v1.patch" of type "application/octet-stream" (1772 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ