On 05/28/2014 02:53 PM, Philipp Kern wrote:
> On Wed, May 28, 2014 at 11:43 PM, Andy Lutomirski <l...@amacapital.net> wrote:
>> However: are you sure that entry_64.S handles this? It looks like
>> tracesys has higher priority than badsys. And strace can certainly
>> see out-of-range syscalls. […]
>
> Not only can it see them: It must see that this bit is set as that's
> the only identifier it has to deduce that the binary is running in x32
> mode.
Yes... keep in mind the ABI is a local property: just because the binary
is running in x32 mode doesn't mean it can't access x86-64 or i386
system calls (or similar for x86-64 processes.) A process started in
i386 mode can transition to long mode and execute x86-64 or x32 system
calls, too.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
