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, 14 Jul 2014 15:23:19 -0700
From:	"H. Peter Anvin" <>
To:	Andy Lutomirski <>
CC:	Konrad Rzeszutek Wilk <>,
	"" <>
Subject: Re: Is espfix64's double-fault thing OK on Xen?

On 07/14/2014 02:35 PM, Andy Lutomirski wrote:
> Presumably the problem is here:
> ENTRY(xen_iret)
>     pushq $0
> 1:    jmp hypercall_iret
> ENDPATCH(xen_iret)
> This seems rather unlikely to work on the espfix stack.
> Maybe espfix64 should be disabled when running on Xen and Xen should
> implement its own espfix64 in the hypervisor.

Perhaps the first question is: is espfix even necessary on Xen?  How
does the Xen PV IRET handle returning to a 16-bit stack segment?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists