From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.2-rc2
Date: Thu, 29 Dec 2022 16:32:57 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Set of fixes for io_uring that should go into the 6.2 release:
- Two fixes for mutex grabbing when the task state is != TASK_RUNNING
(me)
- Check for invalid opcode in io_uring_register() a bit earlier, to
avoid going through the quiesce machinery just to return -EINVAL later
in the process (me)
- Fix for the uapi io_uring header, skipping including time_types.h when
necessary (Stefan)
Please pull!
The following changes since commit 5ad70eb27d2b87ec722fedd23638354be37ea0b0:
MAINTAINERS: io_uring: Add include/trace/events/io_uring.h (2022-12-19 09:56:09 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.2-2022-12-29
for you to fetch changes up to 9eb803402a2a83400c6c6afd900e3b7c87c06816:
uapi:io_uring.h: allow linux/time_types.h to be skipped (2022-12-27 07:32:51 -0700)
----------------------------------------------------------------
io_uring-6.2-2022-12-29
----------------------------------------------------------------
Jens Axboe (3):
io_uring: finish waiting before flushing overflow entries
io_uring/cancel: re-grab ctx mutex after finishing wait
io_uring: check for valid register opcode earlier
Stefan Metzmacher (1):
uapi:io_uring.h: allow linux/time_types.h to be skipped
include/uapi/linux/io_uring.h | 8 ++++++++
io_uring/cancel.c | 9 ++++-----
io_uring/io_uring.c | 30 +++++++++++++++++++-----------
3 files changed, 31 insertions(+), 16 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-12-29 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 23:32 Jens Axboe [this message]
2022-12-30 1:01 ` [GIT PULL] io_uring fixes for 6.2-rc2 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