Hi Geert,
On 28/06/21 7:25 pm, Geert Uytterhoeven wrote:
On Thu, Jun 24, 2021 at 2:46 AM Michael Schmitz <schmitzmic@xxxxxxxxx> wrote:
m68k (other than Coldfire) uses syscall_trace for both trace entry
and trace exit. Seccomp support requires separate entry points for
trace entry and exit which are already provided for Coldfire.
Replace syscall_trace by syscall_trace_enter and syscall_trace_leave
in preparation for seccomp support. Check return code of
syscall_trace_enter(), and skip syscall if -1. Return code will be
left at what had been set by ptrace or seccomp (in regs->d0).
No regression seen in testing with strace on ARAnyM.
Signed-off-by: Michael Schmitz <schmitzmic@xxxxxxxxx>
Thanks for your patch!
arch/m68k/kernel/entry.S | 8 +++++---
We need similar changes to arch/m68k/68000/entry.S and
arch/m68k/coldfire/entry.S
Ouch - I misparsed the #endif right above ENTRY(syscall) and thought the
syscall trace entry code was common for all.
Will fix ... but that will have to be tested by someone else!
Cheers,
Michael
arch/m68k/kernel/ptrace.c | 17 -----------------
2 files changed, 5 insertions(+), 20 deletions(-)
Gr{oetje,eeting}s,
Geert
