From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 5.15-rc3
Date: Sat, 25 Sep 2021 14:32:38 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
This one looks a bit bigger than it is, but that's mainly because 2/3 of
it is enabling IORING_OP_CLOSE to close direct file descriptors. We've
had a few folks using them and finding it confusing that the way to
close them is through using -1 for file update, this just brings API
symmetry for direct descriptors. Hence I think we should just do this
now and have a better API for 5.15 release. There's some room for
de-duplicating the close code, but we're leaving that for the next merge
window.
Outside of that, just small fixes:
- Poll race fixes (Hao)
- io-wq core dump exit fix (me)
- Reschedule around potentially intensive tctx and buffer iterators on
teardown (me)
- Fix for always ending up punting files update to io-wq (me)
- Put the provided buffer meta data under memcg accounting (me)
- Tweak for io_write(), removing dead code that was added with the
iterator changes in this release (Pavel)
Please pull!
The following changes since commit e4e737bb5c170df6135a127739a9e6148ee3da82:
Linux 5.15-rc2 (2021-09-19 17:28:22 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/io_uring-5.15-2021-09-25
for you to fetch changes up to 7df778be2f61e1a23002d1f2f5d6aaf702771eb8:
io_uring: make OP_CLOSE consistent with direct open (2021-09-24 14:07:54 -0600)
----------------------------------------------------------------
io_uring-5.15-2021-09-25
----------------------------------------------------------------
Hao Xu (3):
io_uring: fix race between poll completion and cancel_hash insertion
io_uring: fix missing set of EPOLLONESHOT for CQ ring overflow
io_uring: fix potential req refcount underflow
Jens Axboe (4):
io-wq: ensure we exit if thread group is exiting
io_uring: allow conditional reschedule for intensive iterators
io_uring: put provided buffer meta data under memcg accounting
io_uring: don't punt files update to io-wq unconditionally
Pavel Begunkov (2):
io_uring: kill extra checks in io_write()
io_uring: make OP_CLOSE consistent with direct open
fs/io-wq.c | 3 ++-
fs/io_uring.c | 85 ++++++++++++++++++++++++++++++++++++++++++++++++-----------
2 files changed, 72 insertions(+), 16 deletions(-)
--
Jens Axboe
next reply other threads:[~2021-09-25 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 20:32 Jens Axboe [this message]
2021-09-25 23:05 ` [GIT PULL] io_uring fixes for 5.15-rc3 Linus Torvalds
2021-09-26 1:20 ` Jens Axboe
2021-09-27 13:51 ` Eric W. Biederman
2021-09-27 14:29 ` Jens Axboe
2021-09-27 14:59 ` Jens Axboe
2021-09-27 15:13 ` Eric W. Biederman
2021-09-27 15:41 ` Jens Axboe
2021-09-27 15:52 ` Eric W. Biederman
2021-09-27 16:03 ` Jens Axboe
2021-09-26 4:31 ` Eric W. Biederman
2021-09-25 23:05 ` 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