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 6.15-rc2
Date: Thu, 10 Apr 2025 07:24:52 -0600 [thread overview]
Message-ID: <69eb3ff6-ae4c-47be-86ef-b83fc8327a3e@kernel.dk> (raw)
Hi Linus,
A few small fixes that should go into the 6.15 kernel release. This pull
request contains:
- Reject zero sized legacy provided buffers upfront. No ill side effects
from this one, only really done to shut up a silly syzbot test case.
- Fix for a regression in tag posting for registered files or buffers,
where the tag would be posted even when the registration failed.
- 2 minor zcrx cleanups for code added this merge window.
Please pull!
The following changes since commit e48e99b6edf41c69c5528aa7ffb2daf3c59ee105:
Merge tag 'pull-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2025-04-03 21:12:48 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.15-20250410
for you to fetch changes up to cf960726eb65e8d0bfecbcce6cf95f47b1ffa6cc:
io_uring/kbuf: reject zero sized provided buffers (2025-04-07 07:51:23 -0600)
----------------------------------------------------------------
io_uring-6.15-20250410
----------------------------------------------------------------
Jens Axboe (1):
io_uring/kbuf: reject zero sized provided buffers
Pavel Begunkov (3):
io_uring: don't post tag CQEs on file/buffer registration failure
io_uring/zcrx: put refill data into separate cache line
io_uring/zcrx: separate niov number from pages
io_uring/kbuf.c | 2 ++
io_uring/rsrc.c | 17 ++++++++++++++++-
io_uring/zcrx.c | 19 ++++++++++---------
io_uring/zcrx.h | 5 +++--
4 files changed, 31 insertions(+), 12 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-04-10 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 13:24 Jens Axboe [this message]
2025-04-10 14:09 ` [GIT PULL] io_uring fixes for 6.15-rc2 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=69eb3ff6-ae4c-47be-86ef-b83fc8327a3e@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.