History

signal: don't allow sending any signals to PF_IO_WORKER threads

They don't take signals individually, and even if they share signals with the parent task, don't allow them to be delivered through the worker thread. Linux does allow this kind of behavior for regular threads, but it's really a compatability thing that we need not care about for the IO threads.

Jens Axboe committed 5 years ago

Commit 5be28c81 parent de75a3d1 file · +3 −0Browse files

Unified · Split

kernel/signal.c+3−0
@@ -833,6 +833,9 @@ static int check_kill_permission(int sig, struct kernel_siginfo *info, · 832 unmodified lines
833 833
834 if (!valid_signal(sig))834 if (!valid_signal(sig))
835 return -EINVAL;835 return -EINVAL;
836 /* PF_IO_WORKER threads don't take any signals */
837 if (t->flags & PF_IO_WORKER)
838 return -ESRCH;
836 839
837 if (!si_fromuser(info))840 if (!si_fromuser(info))
838 return 0;841 return 0;

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t