linux-kernel - Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup

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:	Mon, 21 Aug 2006 14:02:16 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Andi Kleen <ak@...e.de>
Cc:	vgoyal@...ibm.com, Magnus Damm <magnus.damm@...il.com>,
	Magnus Damm <magnus@...inux.co.jp>, fastboot@...ts.osdl.org,
	linux-kernel@...r.kernel.org, ebiederm@...ssion.com
Subject: Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.

Andi Kleen <ak@...e.de> writes:

> On Monday 21 August 2006 16:46, Vivek Goyal wrote:
>> On Mon, Aug 21, 2006 at 04:24:10PM +0200, Andi Kleen wrote:
>> > 
>> > > Given the idea of relocatable kernel is floating around I would prefer if
>> > > we are not bounded by the restriction of loading a kernel in lowest 4G.
>> > 
>> > There is already other code that requires this. In fact i don't think it can
>> > be above 40MB currently.
>> >
>> 
>> But I think Eric's prototype patches for relocatable kernel do get over
>> this limitation (Hope I understood the code right). Assuming that relocatable
>> kernel patches will be merged down the line, it would be nice not to be
>> bound by 4G limitation.
>
> He may have fixed the 40MB issue, but I very much doubt he changed the 2GB
> limitation because that would be a major change.

I'm not certain I caught everything but as far as I know I did.
Part of that was by having the code run at a fixed virtual address so
we still live in the last 2GB of the virtual address space.


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