linux-kernel - Re: [PATCH v6 19/27] x86, boot: update comments about entries for 64bit image

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: <50CA78AC.3060700@zytor.com>
Date:	Thu, 13 Dec 2012 16:54:04 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 19/27] x86, boot: update comments about entries for
 64bit image

On 12/13/2012 04:51 PM, Yinghai Lu wrote:
> On Thu, Dec 13, 2012 at 4:44 PM, Yinghai Lu <yinghai@...nel.org> wrote:
>> On Thu, Dec 13, 2012 at 4:38 PM, H. Peter Anvin <hpa@...or.com> wrote:
>>> On 12/13/2012 04:13 PM, Yinghai Lu wrote:
>>>
>>> It is definitely the minmum we can rely on, and so is the minimum we should
>>> rely on.  In fact, we don't even need .bss/.brk to be mapped, but we
>>> probably should require that as a matter of protocol.
>>
>> in my version of arch/x86/kernel/head_64.S is using BRK to do
>> ident/kernel high mapping
>> for kernel that is above 4G.
>> so .brk is needed.
>
> also need to make sure zero page and command line get ident mapping.
> because arch/x86/boot/compressed/head_64.S is using them.
>

... or we need to do the same kind of thing there.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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