From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.2-rc3
Date: Fri, 6 Jan 2023 09:25:13 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
A few minor fixes that should go into the 6.2 release:
- Fix for a memory leak in io-wq worker creation, if we ultimately end
up canceling the worker creation before it gets created (me)
- lockdep annotations for the CQ locking (Pavel)
- A regression fix for CQ timeout handling (Pavel)
- Ring pinning around deferred task_work fix (Pavel)
- A trivial member move in struct io_ring_ctx, saving us some memory
(me)
Please pull!
The following changes since commit 9eb803402a2a83400c6c6afd900e3b7c87c06816:
uapi:io_uring.h: allow linux/time_types.h to be skipped (2022-12-27 07:32:51 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-2023-01-06
for you to fetch changes up to 12521a5d5cb7ff0ad43eadfc9c135d86e1131fa8:
io_uring: fix CQ waiting timeout handling (2023-01-05 08:04:47 -0700)
----------------------------------------------------------------
io_uring-2023-01-06
----------------------------------------------------------------
Jens Axboe (2):
io_uring/io-wq: free worker if task_work creation is canceled
io_uring: move 'poll_multi_queue' bool in io_ring_ctx
Pavel Begunkov (3):
io_uring: pin context while queueing deferred tw
io_uring: lockdep annotate CQ locking
io_uring: fix CQ waiting timeout handling
include/linux/io_uring_types.h | 3 ++-
io_uring/io-wq.c | 1 +
io_uring/io_uring.c | 19 ++++++++++++-------
io_uring/io_uring.h | 15 +++++++++++++++
4 files changed, 30 insertions(+), 8 deletions(-)
--
Jens Axboe
next reply other threads:[~2023-01-06 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 16:25 Jens Axboe [this message]
2023-01-06 21:19 ` [GIT PULL] io_uring fixes for 6.2-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