Eric W. Biederman 7c5d8fa6fb task_work: Decouple TIF_NOTIFY_SIGNAL and task_work ... There are a small handful of reasons besides pending signals that the kernel might want to break out of interruptible sleeps. The flag TIF_NOTIFY_SIGNAL and the helpers that set and clear TIF_NOTIFY_SIGNAL provide that the infrastructure for breaking out of interruptible sleeps and entering the return to user space slow path for those cases. Expand tracehook_notify_signal inline in it's callers and remove it, which makes clear that TIF_NOTIFY_SIGNAL and task_work are separate concepts. Update the comment on set_notify_signal to more accurately describe it's purpose. Reviewed-by: Kees Cook <keescook@chromium.org> Link: https://lkml.kernel.org/r/20220309162454.123006-9-ebiederm@xmission.com Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>		2022-03-10 16:51:50 -06:00
..
common.c	task_work: Call tracehook_notify_signal from get_signal on all architectures	2022-03-10 16:51:36 -06:00
common.h	kernel: Implement selective syscall userspace redirection	2020-12-02 15:07:56 +01:00
kvm.c	task_work: Decouple TIF_NOTIFY_SIGNAL and task_work	2022-03-10 16:51:50 -06:00
Makefile	kernel: Implement selective syscall userspace redirection	2020-12-02 15:07:56 +01:00
syscall_user_dispatch.c	signal: Replace force_fatal_sig with force_exit_sig when in doubt	2021-11-19 09:15:58 -06:00