diff options
author | Jens Axboe <axboe@kernel.dk> | 2021-03-25 18:18:15 -0600 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2021-03-27 14:09:10 -0600 |
commit | 5a842a7448bbfa9bda0a74ca4f239c1b02bb98d8 (patch) | |
tree | 748d031df2d508ca55cd4db4485c3752901b8ce8 /kernel/signal.c | |
parent | b16b3855d89fba640996fefdd3a113c0aa0e380d (diff) | |
download | linux-5a842a7448bbfa9bda0a74ca4f239c1b02bb98d8.tar.bz2 |
Revert "signal: don't allow sending any signals to PF_IO_WORKER threads"
This reverts commit 5be28c8f85ce99ed2d329d2ad8bdd18ea19473a5.
IO threads now take signals just fine, so there's no reason to limit them
specifically. Revert the change that prevented that from happening.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'kernel/signal.c')
-rw-r--r-- | kernel/signal.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/kernel/signal.c b/kernel/signal.c index d22177d37b21..9e172b9341f4 100644 --- a/kernel/signal.c +++ b/kernel/signal.c @@ -834,9 +834,6 @@ static int check_kill_permission(int sig, struct kernel_siginfo *info, if (!valid_signal(sig)) return -EINVAL; - /* PF_IO_WORKER threads don't take any signals */ - if (t->flags & PF_IO_WORKER) - return -ESRCH; if (!si_fromuser(info)) return 0; |