linux-kernel - Re: [PATCH] [RFC] syscalls,x86: Add execveat() system call (v2)

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

Date:	Wed, 01 Aug 2012 17:52:29 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Meredydd Luff <meredydd@...atehouse.org>
CC:	Ingo Molnar <mingo@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Richard Weinberger <richard@....at>,
	linux-kernel@...r.kernel.org, Kees Cook <keescook@...omium.org>,
	Jeff Dike <jdike@...toit.com>
Subject: Re: [PATCH] [RFC] syscalls,x86: Add execveat() system call (v2)

Sorry misunderstood your offlist mail   I can cook up an x32 binary easily enough.

Meredydd Luff <meredydd@...atehouse.org> wrote:

>On 2 Aug 2012 00:33, "H. Peter Anvin" <hpa@...or.com> wrote:
>> > Sorry, you're right.  The argument vector needs compatibility
>support.
>> >
>> > This means you need an x32 version of the function
>
>This is why I originally asked you (off-list) whether it was okay to
>omit
>x32 support in the initial patch :)
>
>I have x32 code already, but I don't have the toolchain or glibc to
>test
>it. (Nor the pain tolerance to build the bleeding-edge versions on this
>laptop - unless I really, really need to...)
>
>If you (or someone else with a working x32 toolchain) could build a
>static
>binary from a tiny test program, I could test that code and put it back
>in
>the patch.
>
>Meredydd

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
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/