From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] Followup io_uring fixes for 6.1-rc1
Date: Thu, 13 Oct 2022 13:27:43 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
A collection of fixes that ended up either being later than the initial
pull request, or dependent on multiple branches (6.0-late being one of
them) and hence deferred purposely. This pull request contains:
- Cleanup fixes for the single submitter late 6.0 change, which we
pushed to 6.1 to keep the 6.0 changes small (Dylan, Pavel)
- Fix for IORING_OP_CONNECT not handling -EINPROGRESS correctly (me)
- Ensure that the zc sendmsg variant gets audited correctly (me)
- Regression fix from this merge window where kiocb_end_write() doesn't
always gets called, which can cause issues with fs freezing (me)
- Registered files SCM handling fix (Pavel)
- Regression fix for big sqe dumping in fdinfo (Pavel)
- Registered buffers accounting fix (Pavel)
- Remove leftover notification structures, we killed them off late in
6.0 (Pavel)
- Minor optimizations (Pavel)
- Cosmetic variable shadowing fix (Stefan)
Please pull!
The following changes since commit 9d84bb40bcb30a7fa16f33baa967aeb9953dda78:
Merge tag 'drm-next-2022-10-07-1' of git://anongit.freedesktop.org/drm/drm (2022-10-07 09:47:47 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.1-2022-10-13
for you to fetch changes up to 2ec33a6c3cca9fe2465e82050c81f5ffdc508b36:
io_uring/rw: ensure kiocb_end_write() is always called (2022-10-12 16:30:56 -0600)
----------------------------------------------------------------
io_uring-6.1-2022-10-13
----------------------------------------------------------------
Dylan Yudaken (2):
io_uring: simplify __io_uring_add_tctx_node
io_uring: remove io_register_submitter
Jens Axboe (3):
io_uring/net: handle -EINPROGRESS correct for IORING_OP_CONNECT
io_uring/opdef: remove 'audit_skip' from SENDMSG_ZC
io_uring/rw: ensure kiocb_end_write() is always called
Pavel Begunkov (7):
io_uring: limit registration w/ SINGLE_ISSUER
io_uring/af_unix: defer registered files gc to io_uring release
io_uring: correct pinned_vm accounting
io_uring: remove notif leftovers
io_uring: remove redundant memory barrier in io_req_local_work_add
io_uring: optimise locking for local tw with submit_wait
io_uring: fix fdinfo sqe offsets calculation
Stefan Roesch (1):
io_uring: local variable rw shadows outer variable in io_write
include/linux/io_uring_types.h | 5 -----
include/linux/skbuff.h | 2 ++
io_uring/fdinfo.c | 2 +-
io_uring/io_uring.c | 33 +++++++++++++++++++-----------
io_uring/io_uring.h | 18 +++++++++++++++--
io_uring/net.c | 28 +++++++++++++++++++------
io_uring/opdef.c | 1 -
io_uring/rsrc.c | 1 +
io_uring/rw.c | 46 ++++++++++++++++++++++++++++++------------
io_uring/tctx.c | 42 +++++++++++++++++---------------------
io_uring/tctx.h | 6 ++++--
net/unix/garbage.c | 20 ++++++++++++++++++
12 files changed, 138 insertions(+), 66 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-10-13 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 19:27 Jens Axboe [this message]
2022-10-14 5:07 ` [GIT PULL] Followup io_uring fixes for 6.1-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