Linux io-uring development
 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.12-rc2
Date: Fri, 4 Oct 2024 09:10:53 -0600	[thread overview]
Message-ID: <08765cba-88f0-4439-ab81-ce949544cdc0@kernel.dk> (raw)

Hi Linus,

A few minor fixes that should go into 6.12-rc2:

- Fix an error path memory leak, if one part fails to allocate.
  Obviously not something that'll generally hit without error injection.

- Fix an io_req_flags_t cast to make sparse happier.

- Improve the recv multishot termination. Not a bug now, but could be
  one in the future. This makes it do the same thing that recvmsg does
  in terms of when to terminate a request or not.

Please pull!


The following changes since commit 6fa6588e5964473356f0e2a02093ea42a5b3fd56:

  Merge tag 'sched_ext-for-6.12-rc1-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext (2024-09-24 11:33:50 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/io_uring-6.12-20241004

for you to fetch changes up to c314094cb4cfa6fc5a17f4881ead2dfebfa717a7:

  io_uring/net: harden multishot termination case for recv (2024-09-30 08:26:59 -0600)

----------------------------------------------------------------
io_uring-6.12-20241004

----------------------------------------------------------------
Guixin Liu (1):
      io_uring: fix memory leak when cache init fail

Jens Axboe (1):
      io_uring/net: harden multishot termination case for recv

Min-Hua Chen (1):
      io_uring: fix casts to io_req_flags_t

 io_uring/io_uring.c | 7 +++++--
 io_uring/net.c      | 4 +++-
 2 files changed, 8 insertions(+), 3 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2024-10-04 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 15:10 Jens Axboe [this message]
2024-10-04 17:50 ` [GIT PULL] io_uring fixes for 6.12-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=08765cba-88f0-4439-ab81-ce949544cdc0@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