signal: don't allow STOP on PF_IO_WORKER threads
authorEric W. Biederman <ebiederm@xmission.com>
Sun, 21 Mar 2021 15:37:48 +0000 (09:37 -0600)
committerJens Axboe <axboe@kernel.dk>
Sun, 21 Mar 2021 15:41:07 +0000 (09:41 -0600)
commit4db4b1a0d1779dc159f7b87feb97030ec0b12597
tree4a5fda2de8bfda249c99f791346d0f2faff9d4ed
parent5be28c8f85ce99ed2d329d2ad8bdd18ea19473a5
signal: don't allow STOP on PF_IO_WORKER threads

Just like we don't allow normal signals to IO threads, don't deliver a
STOP to a task that has PF_IO_WORKER set. The IO threads don't take
signals in general, and have no means of flushing out a stop either.

Longer term, we may want to look into allowing stop of these threads,
as it relates to eg process freezing. For now, this prevents a spin
issue if a SIGSTOP is delivered to the parent task.

Reported-by: Stefan Metzmacher <metze@samba.org>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
kernel/signal.c