Hi,
now that we have an explicit wake_up_new_task() in order to start the
result from create_io_thread(), we should set things up before calling
wake_up_new_task().
Changes in v3:
- rebased on for-5.13/io_uring.
- I dropped this:
fs/proc: hide PF_IO_WORKER in get_task_cmdline()
- I added:
set_task_comm() overflow checks
Changes in v2:
- I dropped/deferred these changes:
- We no longer allow a userspace process to change
/proc/<pid>/[task/<tid>]/comm
- We dynamically generate comm names (up to 63 chars)
via io_wq_worker_comm(), similar to wq_worker_comm()
Stefan Metzmacher (6):
kernel: always initialize task->pf_io_worker to NULL
io_uring: io_sq_thread() no longer needs to reset
current->pf_io_worker
io-wq: call set_task_comm() before wake_up_new_task()
io_uring: complete sq_thread setup before calling wake_up_new_task()
io-wq: warn about future set_task_comm() overflows.
io_uring: warn about future set_task_comm() overflows.
fs/io-wq.c | 20 ++++++++++++++++----
fs/io_uring.c | 34 +++++++++++++++++++++++-----------
kernel/fork.c | 1 +
3 files changed, 40 insertions(+), 15 deletions(-)
--
2.25.1
