aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/entry
diff options
context:
space:
mode:
authorGabriel Krisman Bertazi <krisman@collabora.com>2021-02-05 13:43:21 -0500
committerThomas Gleixner <tglx@linutronix.de>2021-02-06 00:21:42 +0100
commit36a6c843fd0d8e02506681577e96dabd203dd8e8 (patch)
tree5d235696ba455e2ad85d78592489ad818efdf851 /kernel/entry
parententry: Ensure trap after single-step on system call return (diff)
downloadlinux-dev-36a6c843fd0d8e02506681577e96dabd203dd8e8.tar.xz
linux-dev-36a6c843fd0d8e02506681577e96dabd203dd8e8.zip
entry: Use different define for selector variable in SUD
Michael Kerrisk suggested that, from an API perspective, it is a bad idea to share the PR_SYS_DISPATCH_ defines between the prctl operation and the selector variable. Therefore, define two new constants to be used by SUD's selector variable and update the corresponding documentation and test cases. While this changes the API syscall user dispatch has never been part of a Linux release, it will show up for the first time in 5.11. Suggested-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Link: https://lore.kernel.org/r/20210205184321.2062251-1-krisman@collabora.com
Diffstat (limited to 'kernel/entry')
-rw-r--r--kernel/entry/syscall_user_dispatch.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/kernel/entry/syscall_user_dispatch.c b/kernel/entry/syscall_user_dispatch.c
index b0338a5625d9..c240302f56e2 100644
--- a/kernel/entry/syscall_user_dispatch.c
+++ b/kernel/entry/syscall_user_dispatch.c
@@ -50,10 +50,10 @@ bool syscall_user_dispatch(struct pt_regs *regs)
if (unlikely(__get_user(state, sd->selector)))
do_exit(SIGSEGV);
- if (likely(state == PR_SYS_DISPATCH_OFF))
+ if (likely(state == SYSCALL_DISPATCH_FILTER_ALLOW))
return false;
- if (state != PR_SYS_DISPATCH_ON)
+ if (state != SYSCALL_DISPATCH_FILTER_BLOCK)
do_exit(SIGSYS);
}