From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.5-rc3
Date: Fri, 21 Jul 2023 13:34:11 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
This pull request contains a few fixes:
- Fix for io-wq not always honoring REQ_F_NOWAIT, if it was set and
punted directly (eg via DRAIN) (me)
- Capability check fix (Ondrej)
- Regression fix for the mmap changes that went into 6.4, which
apparently broke IA64. (Helge)
Please pull!
The following changes since commit 8a796565cec3601071cbbd27d6304e202019d014:
io_uring: Use io_schedule* in cqring wait (2023-07-07 11:24:29 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.5-2023-07-21
for you to fetch changes up to 07e981137f17e5275b6fa5fd0c28b0ddb4519702:
ia64: mmap: Consider pgoff when searching for free mapping (2023-07-21 09:41:35 -0600)
----------------------------------------------------------------
io_uring-6.5-2023-07-21
----------------------------------------------------------------
Helge Deller (2):
io_uring: Fix io_uring mmap() by using architecture-provided get_unmapped_area()
ia64: mmap: Consider pgoff when searching for free mapping
Jens Axboe (1):
io_uring: treat -EAGAIN for REQ_F_NOWAIT as final for io-wq
Ondrej Mosnacek (1):
io_uring: don't audit the capability check in io_uring_create()
arch/ia64/kernel/sys_ia64.c | 2 +-
arch/parisc/kernel/sys_parisc.c | 15 ++++++++----
io_uring/io_uring.c | 52 ++++++++++++++++++++---------------------
3 files changed, 37 insertions(+), 32 deletions(-)
--
Jens Axboe
next reply other threads:[~2023-07-21 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 19:34 Jens Axboe [this message]
2023-07-22 18:16 ` [GIT PULL] io_uring fixes for 6.5-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