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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 17 May 2012 20:38:46 -0400
From:	Mike Frysinger <vapier@...too.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"H.J. Lu" <hjl.tools@...il.com>, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, torvalds@...ux-foundation.org,
	mingo@...nel.org, tglx@...utronix.de
Subject: Re: [RFC PATCH 00/10] Use __kernel_[u]long_t for x32 user space compatibility

On Thursday 17 May 2012 20:21:34 H. Peter Anvin wrote:
> On 05/17/2012 05:19 PM, Mike Frysinger wrote:
> > On Thursday 17 May 2012 18:13:26 H.J. Lu wrote:
> >> From: H.J. Lu <hjl.tools@...il.com>
> >> 
> >> This patch set changes a number of places where the kernel
> >> headers are exported to user space and currently use explicit
> >> "long" or "unsigned long" to use __kernel_[u]long_t in order to
> >> be compatible with the x32 user space ABI.  These location are
> >> places where x32 uses the x86-64 ABI.
> >> 
> >> It is quite possible that some, or even all, of these locations
> >> should really use dedicated types, but in the meantime this gives
> >> the correct results which the current headers do not.
> > 
> > tangentially related, but what happened to the x86 asm/ptrace.h
> > patch i sent that changed all the registers from unsigned long to
> > u64 ?  e.g. struct pt_regs { -	unsigned long r15; +	__u64 r15;
> 
> Link please?

https://groups.google.com/group/x32-abi/msg/b0b5be30d7aab1f8
-mike

Download attachment "signature.asc " of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists