public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
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.18-final
Date: Fri, 28 Nov 2025 12:32:52 -0700	[thread overview]
Message-ID: <c7983db3-002d-41a0-bc04-523eceb70748@kernel.dk> (raw)

Hi Linus,

Two fixes that should go into the 6.18 kernel release:

- Ensure that vectored registered buffer imports ties the lifetime of
  those to the zero-copy send notification, not the parent request.

- Fix a bug introduced in this merge window, with the introduction of
  mixed sized CQE support.

Please pull!


The following changes since commit 46447367a52965e9d35f112f5b26fc8ff8ec443d:

  io_uring/cmd_net: fix wrong argument types for skb_queue_splice() (2025-11-20 11:40:15 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-6.18-20251128

for you to fetch changes up to f6dc5a36195d3f5be769f60d6987150192dfb099:

  io_uring: fix mixed cqe overflow handling (2025-11-25 07:03:45 -0700)

----------------------------------------------------------------
io_uring-6.18-20251128

----------------------------------------------------------------
Jens Axboe (1):
      io_uring/net: ensure vectored buffer node import is tied to notification

Pavel Begunkov (1):
      io_uring: fix mixed cqe overflow handling

 io_uring/io_uring.c | 2 ++
 io_uring/net.c      | 6 ++++--
 2 files changed, 6 insertions(+), 2 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2025-11-28 19:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28 19:32 Jens Axboe [this message]
2025-11-28 21:15 ` [GIT PULL] io_uring fixes for 6.18-final 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=c7983db3-002d-41a0-bc04-523eceb70748@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