entry: Support Syscall User Dispatch on common syscall entry
authorGabriel Krisman Bertazi <krisman@collabora.com>
Fri, 27 Nov 2020 19:32:35 +0000 (14:32 -0500)
committerThomas Gleixner <tglx@linutronix.de>
Wed, 2 Dec 2020 14:07:56 +0000 (15:07 +0100)
Syscall User Dispatch (SUD) must take precedence over seccomp and
ptrace, since the use case is emulation (it can be invoked with a
different ABI) such that seccomp filtering by syscall number doesn't
make sense in the first place.  In addition, either the syscall is
dispatched back to userspace, in which case there is no resource for to
trace, or the syscall will be executed, and seccomp/ptrace will execute
next.

Since SUD runs before tracepoints, it needs to be a SYSCALL_WORK_EXIT as
well, just to prevent a trace exit event when dispatch was triggered.
For that, the on_syscall_dispatch() examines context to skip the
tracepoint, audit and other work.

[ tglx: Add a comment on the exit side ]

Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Andy Lutomirski <luto@kernel.org>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Kees Cook <keescook@chromium.org>
Link: https://lore.kernel.org/r/20201127193238.821364-5-krisman@collabora.com
include/linux/entry-common.h
kernel/entry/common.c

index 49b26b2..a6e98b4 100644 (file)
                                 SYSCALL_WORK_SYSCALL_TRACE |           \
                                 SYSCALL_WORK_SYSCALL_EMU |             \
                                 SYSCALL_WORK_SYSCALL_AUDIT |           \
+                                SYSCALL_WORK_SYSCALL_USER_DISPATCH |   \
                                 ARCH_SYSCALL_WORK_ENTER)
 #define SYSCALL_WORK_EXIT      (SYSCALL_WORK_SYSCALL_TRACEPOINT |      \
                                 SYSCALL_WORK_SYSCALL_TRACE |           \
                                 SYSCALL_WORK_SYSCALL_AUDIT |           \
+                                SYSCALL_WORK_SYSCALL_USER_DISPATCH |   \
                                 ARCH_SYSCALL_WORK_EXIT)
 
 /*
index 91e8fd5..e661e70 100644 (file)
@@ -5,6 +5,8 @@
 #include <linux/livepatch.h>
 #include <linux/audit.h>
 
+#include "common.h"
+
 #define CREATE_TRACE_POINTS
 #include <trace/events/syscalls.h>
 
@@ -46,6 +48,16 @@ static long syscall_trace_enter(struct pt_regs *regs, long syscall,
 {
        long ret = 0;
 
+       /*
+        * Handle Syscall User Dispatch.  This must comes first, since
+        * the ABI here can be something that doesn't make sense for
+        * other syscall_work features.
+        */
+       if (work & SYSCALL_WORK_SYSCALL_USER_DISPATCH) {
+               if (syscall_user_dispatch(regs))
+                       return -1L;
+       }
+
        /* Handle ptrace */
        if (work & (SYSCALL_WORK_SYSCALL_TRACE | SYSCALL_WORK_SYSCALL_EMU)) {
                ret = arch_syscall_enter_tracehook(regs);
@@ -230,6 +242,19 @@ static void syscall_exit_work(struct pt_regs *regs, unsigned long work)
 {
        bool step;
 
+       /*
+        * If the syscall was rolled back due to syscall user dispatching,
+        * then the tracers below are not invoked for the same reason as
+        * the entry side was not invoked in syscall_trace_enter(): The ABI
+        * of these syscalls is unknown.
+        */
+       if (work & SYSCALL_WORK_SYSCALL_USER_DISPATCH) {
+               if (unlikely(current->syscall_dispatch.on_dispatch)) {
+                       current->syscall_dispatch.on_dispatch = false;
+                       return;
+               }
+       }
+
        audit_syscall_exit(regs);
 
        if (work & SYSCALL_WORK_SYSCALL_TRACEPOINT)