Hello! Michael and I have been working on SECCOMP in SuperH and successfully added the missing pieces yesterday [1]. We're now looking into what needs to be done for m68k and I have noticed that syscall_trace_enter and syscall_trace_leave - which needs to be touched for SECCOMP support - are available on ColdFire and non-MMU targets for m68k. Is there a particular reason for that? Looking at 68000/entry.S, I can see that both functions are invoked [2] so I'm not sure why they are built for CONFIG_COLDFIRE and !CONFIG_MMM only. Any ideas? Adrian
[1] https://marc.info/?l=linux-sh&m=159546012829989&w=2 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/m68k/68000/entry.S
-- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz@xxxxxxxxxx `. `' Freie Universitaet Berlin - glaubitz@xxxxxxxxxxxxxxxxxxx `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
