linux-kernel - Re: [RFC PATCH 00/10] Use __kernel_[u]long

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: <201205172019.27462.vapier@gentoo.org>
Date:	Thu, 17 May 2012 20:19:25 -0400
From:	Mike Frysinger <vapier@...too.org>
To:	"H.J. Lu" <hjl.tools@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	torvalds@...ux-foundation.org, hpa@...or.com, 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 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;
-mike

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