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.11-rc6
Date: Fri, 30 Aug 2024 14:31:57 -0600 [thread overview]
Message-ID: <791375ed-d460-4fa4-81da-fffea554de2e@kernel.dk> (raw)
Hi Linus,
Here are two fixes that should go into the 6.11 release:
- A fix for a regression that happened in 6.11 merge window, where the
copying of iovecs for compat mode applications got broken for certain
cases.
- Fix for a bug introduced in 6.10, where if using recv/send bundles
with classic provided buffers, the recv/send would fail to set the
right iovec count. This caused 0 byte send/recv results. Found via
code coverage testing and writing a test case to exercise it.
Please pull!
The following changes since commit e0ee967630c8ee67bb47a5b38d235cd5a8789c48:
io_uring/kbuf: sanitize peek buffer setup (2024-08-21 07:16:38 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.11-20240830
for you to fetch changes up to f274495aea7b15225b3d83837121b22ef96e560c:
io_uring/kbuf: return correct iovec count from classic buffer peek (2024-08-30 10:45:54 -0600)
----------------------------------------------------------------
io_uring-6.11-20240830
----------------------------------------------------------------
Jens Axboe (2):
io_uring/rsrc: ensure compat iovecs are copied correctly
io_uring/kbuf: return correct iovec count from classic buffer peek
io_uring/kbuf.c | 2 +-
io_uring/rsrc.c | 19 +++++++++++++++----
2 files changed, 16 insertions(+), 5 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-08-30 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 20:31 Jens Axboe [this message]
2024-08-31 4:11 ` [GIT PULL] io_uring fixes for 6.11-rc6 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=791375ed-d460-4fa4-81da-fffea554de2e@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.