OSDN Git Service

task_work: Decouple TIF_NOTIFY_SIGNAL and task_work
authorEric W. Biederman <ebiederm@xmission.com>
Wed, 9 Feb 2022 17:18:54 +0000 (11:18 -0600)
committerEric W. Biederman <ebiederm@xmission.com>
Thu, 10 Mar 2022 22:51:50 +0000 (16:51 -0600)
commit7c5d8fa6fbb12a3f0eefe8762bfede508e147cb3
tree0abadafb76c2719b1632ae452a228909669edef3
parent8ba62d37949e248c698c26e0d82d72fda5d33ebf
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>
fs/io-wq.c
fs/io_uring.c
include/linux/tracehook.h
kernel/entry/kvm.c