Re: [PATCH 08/17] ptrace/m68k: Stop open coding ptrace_report_syscall
From: Al Viro <viro@zeniv.linux.org.uk>
Date: 2022-01-10 20:37:46
Also in:
linux-arch, linux-m68k, lkml
Possibly related (same subject, not in this thread)
- 2022-01-10 · Re: [PATCH 08/17] ptrace/m68k: Stop open coding ptrace_report_syscall · Eric W. Biederman <hidden>
On Mon, Jan 10, 2022 at 06:54:57PM +0100, Geert Uytterhoeven wrote:
In fact Michael did so in "[PATCH v7 1/2] m68k/kernel - wire up syscall_trace_enter/leave for m68k"[1], but that's still stuck... [1] https://lore.kernel.org/r/1624924520-17567-2-git-send-email-schmitzmic@gmail.com/ (local)
Looks sane, but I'd split it in two - switch to calling syscall_trace_{enter,leave}
and then handling the return values...
The former would keep the current behaviour (modulo reporting enter vs. leave
via PTRACE_GETEVENTMSG), the latter would allow syscall number change by tracer
and/or handling of seccomp/audit/whatnot.
For exit+signal work the former would suffice, and IMO it would be a good idea
to put that one into a shared branch to be pulled both by seccomp and by signal
series. Would reduce the conflicts...
Objections?