From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 5.18-rc1
Date: Fri, 1 Apr 2022 13:31:48 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
A little bit all over the map, some regression fixes for this merge
window, and some general fixes that are stable bound. In detail:
- Fix an SQPOLL memory ordering issue (Almog)
- Accept fixes (Dylan)
- Poll fixes (me)
- Fixes for provided buffers and recycling (me)
- Tweak to IORING_OP_MSG_RING command added in this merge window (me)
- Memory leak fix (Pavel)
- Misc fixes and tweaks (Pavel, me)
Please pull!
The following changes since commit 5e929367468c8f97cd1ffb0417316cecfebef94b:
io_uring: terminate manual loop iterator loop correctly for non-vecs (2022-03-18 11:42:48 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/for-5.18/io_uring-2022-04-01
for you to fetch changes up to 3f1d52abf098c85b177b8c6f5b310e8347d1bc42:
io_uring: defer msg-ring file validity check until command issue (2022-03-29 14:04:28 -0600)
----------------------------------------------------------------
for-5.18/io_uring-2022-04-01
----------------------------------------------------------------
Almog Khaikin (1):
io_uring: fix memory ordering when SQPOLL thread goes to sleep
Dylan Yudaken (2):
io_uring: fix async accept on O_NONBLOCK sockets
io_uring: enable EPOLLEXCLUSIVE for accept poll
Jens Axboe (12):
io_uring: recycle provided before arming poll
io_uring: ensure that fsnotify is always called
io_uring: remove poll entry from list when canceling all
io_uring: bump poll refs to full 31-bits
io_uring: fix assuming triggered poll waitqueue is the single poll
io_uring: don't recycle provided buffer if punted to async worker
io_uring: ensure recv and recvmsg handle MSG_WAITALL correctly
io_uring: add flag for disabling provided buffer recycling
io_uring: remove IORING_CQE_F_MSG
io_uring: improve task work cache utilization
io_uring: fail links if msg-ring doesn't succeeed
io_uring: defer msg-ring file validity check until command issue
Pavel Begunkov (4):
io_uring: improve req fields comments
io_uring: fix invalid flags for io_put_kbuf()
io_uring: fix put_kbuf without proper locking
io_uring: fix memory leak of uid in files registration
fs/io_uring.c | 133 ++++++++++++++++++++++++++++++++++--------
include/uapi/linux/io_uring.h | 2 -
2 files changed, 110 insertions(+), 25 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-04-01 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 19:31 Jens Axboe [this message]
2022-04-01 23:44 ` [GIT PULL] io_uring fixes for 5.18-rc1 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