diff options
| author | Kees Cook <[email protected]> | 2023-08-10 12:54:19 -0700 |
|---|---|---|
| committer | Kees Cook <[email protected]> | 2023-08-16 13:58:49 -0700 |
| commit | 4697b5848bd933f68ebd04836362c8de0cacaf71 (patch) | |
| tree | 25b3e2385221302d871873c25acb54059b44d835 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | cf007647475b5090819c5fe8da771073145c7334 (diff) | |
ARM: ptrace: Restore syscall skipping for tracers
Since commit 4e57a4ddf6b0 ("ARM: 9107/1: syscall: always store
thread_info->abi_syscall"), the seccomp selftests "syscall_errno"
and "syscall_faked" have been broken. Both seccomp and PTRACE depend
on using the special value of "-1" for skipping syscalls. This value
wasn't working because it was getting masked by __NR_SYSCALL_MASK in
both PTRACE_SET_SYSCALL and get_syscall_nr().
Explicitly test for -1 in PTRACE_SET_SYSCALL and get_syscall_nr(),
leaving it exposed when present, allowing tracers to skip syscalls
again.
Cc: Russell King <[email protected]>
Cc: Arnd Bergmann <[email protected]>
Cc: Lecopzer Chen <[email protected]>
Cc: Oleg Nesterov <[email protected]>
Cc: [email protected]
Fixes: 4e57a4ddf6b0 ("ARM: 9107/1: syscall: always store thread_info->abi_syscall")
Reviewed-by: Arnd Bergmann <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Kees Cook <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions