summaryrefslogtreecommitdiffstats
path: root/fs/io_uring.c
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2021-03-09 19:49:02 -0700
committerJens Axboe <axboe@kernel.dk>2021-03-10 07:28:43 -0700
commite22bc9b481a90d7898984ea17621f04a653e2cd1 (patch)
tree9c7f6a4821f3afecdbeca3eb07e2d397e0a3dc4c /fs/io_uring.c
parente8f98f24549d62cc54bf608c815904a56d4437bc (diff)
downloadlinux-stable-e22bc9b481a90d7898984ea17621f04a653e2cd1.tar.gz
linux-stable-e22bc9b481a90d7898984ea17621f04a653e2cd1.tar.bz2
linux-stable-e22bc9b481a90d7898984ea17621f04a653e2cd1.zip
kernel: make IO threads unfreezable by default
The io-wq threads were already marked as no-freeze, but the manager was not. On resume, we perpetually have signal_pending() being true, and hence the manager will loop and spin 100% of the time. Just mark the tasks created by create_io_thread() as PF_NOFREEZE by default, and remove any knowledge of it in io-wq and io_uring. Reported-by: Kevin Locke <kevin@kevinlocke.name> Tested-by: Kevin Locke <kevin@kevinlocke.name> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'fs/io_uring.c')
-rw-r--r--fs/io_uring.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/fs/io_uring.c b/fs/io_uring.c
index 62f998bf2ce8..14165e18020c 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -6733,7 +6733,6 @@ static int io_sq_thread(void *data)
up_read(&sqd->rw_lock);
schedule();
- try_to_freeze();
down_read(&sqd->rw_lock);
list_for_each_entry(ctx, &sqd->ctx_list, sqd_list)
io_ring_clear_wakeup_flag(ctx);