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.2-rc5
Date: Fri, 24 Jul 2026 19:32:39 -0600 [thread overview]
Message-ID: <55fe18a5-1bae-4836-a4de-f7a496165b5e@kernel.dk> (raw)
Hi Linus,
io_uring fixes for this week:
- Fix a missing ERESTARTSYS conversion in the read paths, which got
messed up back when some code consolidation was done for read
multishot support.
- zcrx UAPI rename, dropping the abbreviated "notif" naming in favor of
"event" for consistency and to be less ambiguous for users. This was
added for 7.2, so let's rename it while we still can. No functional or
code changes, just a strict rename.
Please pull!
The following changes since commit 3afc64c61ce906a04f073ca350b46de10e8302f9:
io_uring/bpf-ops: reject re-registration of an already-bound ops (2026-07-17 11:17:54 -0600)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-7.2-20260724
for you to fetch changes up to e366c15e1610ef11d0717ecd875ae63050282676:
io_uring/zcrx: rename notif to event (2026-07-22 09:48:42 -0600)
----------------------------------------------------------------
Pavel Begunkov (3):
io_uring/zcrx: drop "notif" from stats struct names
io_uring/zcrx: rename ZCRX_NOTIF_NO_BUFFERS
io_uring/zcrx: rename notif to event
Yitang Yang (1):
io_uring/rw: fix missing ERESTARTSYS conversion in read paths
include/uapi/linux/io_uring/query.h | 14 ++++++-------
include/uapi/linux/io_uring/zcrx.h | 32 ++++++++++++++--------------
io_uring/query.c | 12 +++++------
io_uring/rw.c | 42 ++++++++++++++++++++++---------------
io_uring/zcrx.c | 34 +++++++++++++++---------------
io_uring/zcrx.h | 7 ++++---
6 files changed, 75 insertions(+), 66 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-07-25 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 1:32 Jens Axboe [this message]
2026-07-25 3:11 ` [GIT PULL] io_uring fixes for 7.2-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=55fe18a5-1bae-4836-a4de-f7a496165b5e@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