summaryrefslogtreecommitdiffstats
path: root/arch/blackfin
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2020-09-12 02:58:26 +0200
committerThomas Gleixner <tglx@linutronix.de>2020-09-14 22:49:51 +0200
commitb6ec413461034d49f9e586845825adb35ba308f6 (patch)
tree1834572ed83f3acea4ef95b18244b3fd78512760 /arch/blackfin
parentLinux 5.9-rc5 (diff)
downloadlinux-b6ec413461034d49f9e586845825adb35ba308f6.tar.xz
linux-b6ec413461034d49f9e586845825adb35ba308f6.zip
core/entry: Report syscall correctly for trace and audit
On v5.8 when doing seccomp syscall rewrites (e.g. getpid into getppid as seen in the seccomp selftests), trace (and audit) correctly see the rewritten syscall on entry and exit: seccomp_bpf-1307 [000] .... 22974.874393: sys_enter: NR 110 (... seccomp_bpf-1307 [000] .N.. 22974.874401: sys_exit: NR 110 = 1304 With mainline we see a mismatched enter and exit (the original syscall is incorrectly visible on entry): seccomp_bpf-1030 [000] .... 21.806766: sys_enter: NR 39 (... seccomp_bpf-1030 [000] .... 21.806767: sys_exit: NR 110 = 1027 When ptrace or seccomp change the syscall, this needs to be visible to trace and audit at that time as well. Update the syscall earlier so they see the correct value. Fixes: d88d59b64ca3 ("core/entry: Respect syscall number rewrites") Reported-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Kees Cook <keescook@chromium.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Link: https://lore.kernel.org/r/20200912005826.586171-1-keescook@chromium.org
Diffstat (limited to 'arch/blackfin')
0 files changed, 0 insertions, 0 deletions