linux-kernel - Re: [GIT PULL] Introduce the X32 binary format on x86, for v3.4

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

Message-ID: <4F726E56.4070405@zytor.com>
Date:	Tue, 27 Mar 2012 18:50:14 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...nel.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] Introduce the X32 binary format on x86, for v3.4

On 03/19/2012 10:50 AM, Ingo Molnar wrote:
> Linus,
> 
> Please pull the latest x86-x32-for-linus git tree from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-x32-for-linus
> 
>    HEAD: 31796ac4e8f0e88f5c10f1ad6dab8f19bebe44a4 x32: Fix alignment fail in struct compat_siginfo
> 
> This tree introduces the X32 binary format and execution mode 
> for x86: 32-bit data space binaries using 64-bit instructions 
> and 64-bit kernel syscalls.
> 
> This allows applications whose working set fits into a 32 bits 
> address space to make use of 64-bit instructions while using a 
> 32-bit address space with shorter pointers, more compressed data 
> structures, etc.
> 

Hi Linus,

Any problem either with this tree and/or the pull request?  The
posix_types.h revamp ended up being part of this request (because x32
depends on it) but is technically standalone.

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