From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.10-rc3
Date: Fri, 7 Jun 2024 09:55:17 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
A few fixes that should go into the 6.10 kernel release:
- Fix a locking order issue with setting max async thread workers
(Hagar)
- Fix for a NULL pointer dereference for failed async flagged requests
using ring provided buffers. This doesn't affect the current kernel,
but it does affect older kernels, and is being queued up for 6.10 just
to make the stable process easier (me)
- Fix for NAPI timeout calculations for how long to busy poll, and
subsequently how much to sleep post that if a wait timeout is passed
in (me)
- Fix for a regression in this release cycle, where we could end up
using a partially unitialized match value for io-wq (Su)
Please pull!
The following changes since commit 18414a4a2eabb0281d12d374c92874327e0e3fe3:
io_uring/net: assign kmsg inq/flags before buffer selection (2024-05-30 14:04:37 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.10-20240607
for you to fetch changes up to 73254a297c2dd094abec7c9efee32455ae875bdf:
io_uring: fix possible deadlock in io_register_iowq_max_workers() (2024-06-04 07:39:17 -0600)
----------------------------------------------------------------
io_uring-6.10-20240607
----------------------------------------------------------------
Hagar Hemdan (1):
io_uring: fix possible deadlock in io_register_iowq_max_workers()
Jens Axboe (2):
io_uring: check for non-NULL file pointer in io_file_can_poll()
io_uring/napi: fix timeout calculation
Su Hui (1):
io_uring/io-wq: avoid garbage value of 'match' in io_wq_enqueue()
io_uring/io-wq.c | 10 +++++-----
io_uring/io_uring.h | 2 +-
io_uring/napi.c | 24 +++++++++++++-----------
io_uring/register.c | 4 ++++
4 files changed, 23 insertions(+), 17 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-06-07 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 15:55 Jens Axboe [this message]
2024-06-07 23:51 ` [GIT PULL] io_uring fixes for 6.10-rc3 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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