linux-kernel - Re: [patch 17/24] Xen-paravirt_ops: avoid having a bad selector in %gs during context switch

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-next>] [day] [month] [year] [list]

Message-Id: <200702212310.02218.ak@suse.de>
Date:	Wed, 21 Feb 2007 23:10:02 +0100
From:	Andi Kleen <ak@...e.de>
To:	virtualization@...ts.osdl.org
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Chris Wright <chrisw@...s-sol.org>,
	xen-devel@...ts.xensource.com,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch 17/24] Xen-paravirt_ops: avoid having a bad selector in %gs during context switch


>  	/*
> +	 * Temporary hack: zero gs now that we've saved it so that Xen
> +	 * doesn't try to reload the old value after changing the GDT
> +	 * during the context switch.  This can go away once Xen has
> +	 * been taught to only reload %gs when it absolutely must.
> +	 */
> +	loadsegment(gs, 0);

Sorry, but i don't really want that unconditionally in the context switch.
Adding a paravirt ops for it would be also ugly. Can Xen be fixed?

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