Re: [PATCH] x32: Mask away the x32 syscall bit in the ptrace codepath

[Andy Lutomirski]

On Wed, May 28, 2014 at 2:53 PM, Philipp Kern <pkern@xxxxxxxxxx> wrote:
> On Wed, May 28, 2014 at 11:43 PM, Andy Lutomirski <luto@xxxxxxxxxxxxxx> 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.
>
> Out of range syscall numbers certainly do not work for auditing right
> now, hence my attempt to patch around it.

There appears to be a completely arbitrary limit of 32*64 syscalls.
There's also an arbitrary limit of 4 arguments.  Both are wrong.  I
have no intention of fixing either.

I'll fix the OOPS, though.

>
> Kind regards and thanks
> Philipp Kern



-- 
Andy Lutomirski
AMA Capital Management, LLC
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/