WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [PATCH 2/7] x86_64: syscall argument clobber check

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH 2/7] x86_64: syscall argument clobber check
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 23 Aug 2006 11:00:56 +0200
Delivery-date: Wed, 23 Aug 2006 02:00:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
(noticed during preparation of initial PAE-guest-on-64bit patches)
The offset used to compare the return IP was apparently wrong; I
didn't actually test that things didn't work as intended (or that they
do now with this change), it just caught my eye that the UREGS_rip
access a little further up in the same function was done with
adjustment for the extra item on the stack, but this one wasn't.

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>

Attachment: x86_64-clobber-check.patch
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH 2/7] x86_64: syscall argument clobber check, Jan Beulich <=