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.0-rc5
Date: Fri, 20 Mar 2026 10:16:19 -0600 [thread overview]
Message-ID: <40c31f28-a227-4123-91fd-5a4b0c044bef@kernel.dk> (raw)
Hi Linus,
Three fixes for io_uring that should go into this release, all headed to
stable. This pull request contains:
- A bit of a work-around for AF_UNIX recv multishot, as the in-kernel
implementation doesn't properly signal EOF. We'll likely rework this
one going forward, but the fix is sufficient for now.
- Two fixes for incrementally consumed buffers, for non-pollable files
and for 0 byte reads.
Please pull!
The following changes since commit c2c185be5c85d37215397c8e8781abf0a69bec1f:
io_uring/kbuf: check if target buffer list is still legacy on recycle (2026-03-12 08:59:25 -0600)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-7.0-20260320
for you to fetch changes up to 418eab7a6f3c002d8e64d6e95ec27118017019af:
io_uring/kbuf: propagate BUF_MORE through early buffer commit path (2026-03-19 15:09:48 -0600)
----------------------------------------------------------------
io_uring-7.0-20260320
----------------------------------------------------------------
Jens Axboe (3):
io_uring/poll: fix multishot recv missing EOF on wakeup race
io_uring/kbuf: fix missing BUF_MORE for incremental buffers at EOF
io_uring/kbuf: propagate BUF_MORE through early buffer commit path
include/linux/io_uring_types.h | 3 +++
io_uring/kbuf.c | 14 +++++++++++---
io_uring/poll.c | 9 +++++++--
3 files changed, 21 insertions(+), 5 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-03-20 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 16:16 Jens Axboe [this message]
2026-03-20 17:14 ` [GIT PULL] io_uring fixes for 7.0-rc5 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=40c31f28-a227-4123-91fd-5a4b0c044bef@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox