Hi Linus, Was planning on holding these for -rc5, but I think we may as well flush them out. In this pull request: - The SIGSTOP change from Eric, so we properly ignore that for PF_IO_WORKER threads. - Disallow sending signals to PF_IO_WORKER threads in general, we're not interested in having them funnel back to the io_uring owning task. - Stable fix from Stefan, ensuring we properly break links for short send/sendmsg recv/recvmsg if MSG_WAITALL is set. - Catch and loop when needing to run task_work before a PF_IO_WORKER threads goes to sleep. Please pull! The following changes since commit de75a3d3f5a14c9ab3c4883de3471d3c92a8ee78: io_uring: don't leak creds on SQO attach error (2021-03-18 09:44:35 -0600) are available in the Git repository at: git://git.kernel.dk/linux-block.git tags/io_uring-5.12-2021-03-21 for you to fetch changes up to 0031275d119efe16711cd93519b595e6f9b4b330: io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with MSG_WAITALL (2021-03-21 09:41:14 -0600) ---------------------------------------------------------------- io_uring-5.12-2021-03-21 ---------------------------------------------------------------- Eric W. Biederman (1): signal: don't allow STOP on PF_IO_WORKER threads Jens Axboe (2): signal: don't allow sending any signals to PF_IO_WORKER threads io-wq: ensure task is running before processing task_work Stefan Metzmacher (1): io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with MSG_WAITALL fs/io-wq.c | 8 ++++++-- fs/io_uring.c | 24 ++++++++++++++++++++---- kernel/signal.c | 6 +++++- 3 files changed, 31 insertions(+), 7 deletions(-) -- Jens Axboe