linux-kernel - X32 syscall number base

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]

Message-Id: <201103170446.12011.vapier@gentoo.org>
Date:	Thu, 17 Mar 2011 04:46:11 -0400
From:	Mike Frysinger <vapier@...too.org>
To:	"H.J. Lu" <hjl.tools@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, x32-abi@...glegroups.com
Subject: X32 syscall number base

in looking at how syscalls are implemented, i see that you've picked a base of 
4096.  so syscall numbers [0...4096) are for x86_64 and [4096...-1) are for 
x32.  this 4096 limit is a bit low isnt it ?  seems like the best bet would be 
to bisect the available space for each new ABI ...

ARM EABI picked 0x900000 for their base when adding a new ABI ...
-mike

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