From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: [GIT PULL] io_uring fixes for 7.3-rc3
Date: Fri, 11 Sep 2026 05:33:06 -0600 [thread overview]
Message-ID: <3764292c-52f5-47ce-8f2c-02663e1f287d@kernel.dk> (raw)
Hi Linus,
A few io_uring fixes for this week. This pull request contains:
- Fix a deadlock in the write path with superblock freezing.
- Fix an issue where a provided buffer ring would overconsume when using
MSG_TRUNC.
- Keep the CQE flags on iopoll requests when adding kbuf flags
Please pull!
The following changes since commit 2cf20c4e0f72d523b8673053e7120d092ff1f074:
io_uring/waitid: avoid siginfo copy during ring teardown (2026-08-25 11:51:38 -0600)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-7.3-20260911
for you to fetch changes up to 47ccc3f1c615a46c25cbf7f3ae60df30b40eb2e6:
io_uring/rw: keep CQE flags on iopoll requests when adding kbuf flags (2026-09-09 09:59:02 -0600)
----------------------------------------------------------------
io_uring-7.3-20260911
----------------------------------------------------------------
Caleb Sander Mateos (1):
io_uring/rw: keep CQE flags on iopoll requests when adding kbuf flags
Gabriel Krisman Bertazi (2):
io_uring/net: let io_recv_buf_select return the length of the buffer region
io_uring/net: don't overconsume buffers when using MSG_TRUNC
Jens Axboe (1):
io_uring/rw: end write accounting from ->ki_complete
io_uring/net.c | 51 +++++++++++++++++++++++++++++++++++++++------------
io_uring/rw.c | 32 +++++++++++++++++++++-----------
2 files changed, 60 insertions(+), 23 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-09-11 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 11:33 Jens Axboe [this message]
2026-09-11 20:24 ` [GIT PULL] io_uring fixes for 7.3-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 \
--in-reply-to=3764292c-52f5-47ce-8f2c-02663e1f287d@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.