linux-kernel - Re: [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]

Message-Id: <200608211219.09042.ak@suse.de>
Date:	Mon, 21 Aug 2006 12:19:09 +0200
From:	Andi Kleen <ak@...e.de>
To:	Magnus Damm <magnus@...inux.co.jp>
Cc:	fastboot@...ts.osdl.org, linux-kernel@...r.kernel.org,
	ebiederm@...ssion.com
Subject: Re: [PATCH][RFC] x86_64: Reload CS when startup_64 is used.


>  
> +	/* Reload CS with a value that is within our GDT. We need to do this
> +	 * if we were loaded by a 64 bit bootloader that happened to use a 
> +	 * CS that is larger than the GDT limit. This is true if we came here
> +	 * from kexec running under Xen.
> +	 */
> +	movq	%rsp, %rdx
> +	movq	$__KERNEL_DS, %rax
> +	pushq	%rax /* SS */
> +	pushq	%rdx /* RSP */
> +	movq	$__KERNEL_CS, %rax
> +	movq	$cs_reloaded, %rdx
> +	pushq	%rax /* CS */
> +	pushq	%rdx /* RIP */
> +	lretq

Can't you just use a normal far jump? That might be simpler.

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