diff options
| author | Eric W. Biederman <[email protected]> | 2022-02-09 17:18:54 +0000 |
|---|---|---|
| committer | Eric W. Biederman <[email protected]> | 2022-03-10 22:51:50 +0000 |
| commit | 7c5d8fa6fbb12a3f0eefe8762bfede508e147cb3 (patch) | |
| tree | 0abadafb76c2719b1632ae452a228909669edef3 /fs/proc/array.c | |
| parent | task_work: Call tracehook_notify_signal from get_signal on all architectures (diff) | |
| download | kernel-7c5d8fa6fbb12a3f0eefe8762bfede508e147cb3.tar.gz kernel-7c5d8fa6fbb12a3f0eefe8762bfede508e147cb3.zip | |
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 <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: "Eric W. Biederman" <[email protected]>
Diffstat (limited to 'fs/proc/array.c')
0 files changed, 0 insertions, 0 deletions