From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: [GIT PULL] io_uring fix for 6.19-rc5
Date: Fri, 9 Jan 2026 11:44:27 -0700 [thread overview]
Message-ID: <107197ad-1de3-4773-89ad-a3c1977dd7eb@kernel.dk> (raw)
Hi Linus,
Single fix for a regression introduced in 6.15, where a failure to wake
up idle io-wq workers at ring exit will wait for the timeout to expire.
This isn't normally noticeable, as the exit is async. But if a parent
task created a thread that sets up a ring and uses requests that cause
io-wq threads to be created, and the parent task then waits for the
thread to exit, then it can take 5 seconds for that pthread_join() to
succeed as the child thread is waiting for its children to exit.
On top of that, just a basic cleanup as well.
Please pull!
The following changes since commit 70eafc743016b1df73e00fd726ffedd44ce1bdd3:
io_uring/memmap: drop unused sz param in io_uring_validate_mmap_request() (2026-01-01 08:16:48 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-6.19-20260109
for you to fetch changes up to e4fdbca2dc774366aca6532b57bfcdaae29aaf63:
io_uring/io-wq: remove io_wq_for_each_worker() return value (2026-01-05 15:39:20 -0700)
----------------------------------------------------------------
io_uring-6.19-20260109
----------------------------------------------------------------
Jens Axboe (2):
io_uring/io-wq: fix incorrect io_wq_for_each_worker() termination logic
io_uring/io-wq: remove io_wq_for_each_worker() return value
io_uring/io-wq.c | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-01-09 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 18:44 Jens Axboe [this message]
2026-01-10 2:15 ` [GIT PULL] io_uring fix for 6.19-rc5 pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=107197ad-1de3-4773-89ad-a3c1977dd7eb@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox