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]
Date:	Wed, 6 Mar 2013 14:19:14 -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:14 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Wed, Mar 6, 2013 at 1:49 PM, H. Peter Anvin <hpa@...ux.intel.com> wrote:
>> On 03/06/2013 01:33 PM, Yinghai Lu wrote:
>>> On Wed, Mar 6, 2013 at 12:58 PM, H. Peter Anvin <hpa@...ux.intel.com> wrote:
>>>
>>>> Excellent.  Yinghai, can you write up the patch with a proper
>>>> description and I'll put it into x86/urgent.
>>>
>>> I made it more robust: make sure real_end have 8M below it.
>>> Please check attached one.
>>>
>>
>> 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.
>
> Henrik's system has 5M holes, so i picked 8M.
>
> Current what is minimum ram is required for boot x86 32bit kernel? 8M?

just check the code again, it should be ok.

we can not find the 8M, real_end will set to 8M anyway. as the
memblock_find_in_range will return
0.

then will map [0, 8M] at first, then will map [8M, whatever).

Thanks

Yinghai
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ