entry: Add support for TIF_NOTIFY_SIGNAL
Add TIF_NOTIFY_SIGNAL handling in the generic entry code, which if set, will return true if signal_pending() is used in a wait loop. That causes an exit of the loop so that notify_signal tracehooks can be run. If the wait loop is currently inside a system call, the system call is restarted once task_work has been processed. In preparation for only having arch_do_signal() handle syscall restarts if _TIF_SIGPENDING isn't set, rename it to arch_do_signal_or_restart(). Pass in a boolean that tells the architecture specific signal handler if it should attempt to get a signal, or just process a potential syscall restart. For !CONFIG_GENERIC_ENTRY archs, add the TIF_NOTIFY_SIGNAL handling to get_signal(). This is done to minimize the needed architecture changes to support this feature. Signed-off-by:Jens Axboe <axboe@kernel.dk> Signed-off-by:
Thomas Gleixner <tglx@linutronix.de> Reviewed-by:
Oleg Nesterov <oleg@redhat.com> Link: https://lore.kernel.org/r/20201026203230.386348-3-axboe@kernel.dk
Showing
- arch/x86/kernel/signal.c 2 additions, 2 deletionsarch/x86/kernel/signal.c
- include/linux/entry-common.h 8 additions, 3 deletionsinclude/linux/entry-common.h
- include/linux/entry-kvm.h 2 additions, 2 deletionsinclude/linux/entry-kvm.h
- include/linux/sched/signal.h 10 additions, 1 deletioninclude/linux/sched/signal.h
- include/linux/tracehook.h 27 additions, 0 deletionsinclude/linux/tracehook.h
- kernel/entry/common.c 11 additions, 3 deletionskernel/entry/common.c
- kernel/entry/kvm.c 3 additions, 0 deletionskernel/entry/kvm.c
- kernel/signal.c 14 additions, 0 deletionskernel/signal.c
Loading
Please register or sign in to comment