public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.7-rc5
Date: Fri, 8 Dec 2023 10:48:48 -0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

Two minor fixes for issues introduced in this release cycle, and two
fixes for issues or potential issues that are heading to stable. One of
these ends up disabling passing io_uring file descriptors via
SCM_RIGHTS. There really shouldn't be an overlap between that kind of
historic use case and modern usage of io_uring, which is why this was
deemed appropriate.

Please pull!


The following changes since commit 73363c262d6a7d26063da96610f61baf69a70f7c:

  io_uring: use fget/fput consistently (2023-11-28 11:56:29 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/io_uring-6.7-2023-12-08

for you to fetch changes up to 705318a99a138c29a512a72c3e0043b3cd7f55f4:

  io_uring/af_unix: disable sending io_uring over sockets (2023-12-07 10:35:19 -0700)

----------------------------------------------------------------
io_uring-6.7-2023-12-08

----------------------------------------------------------------
Dan Carpenter (1):
      io_uring/kbuf: Fix an NULL vs IS_ERR() bug in io_alloc_pbuf_ring()

Jens Axboe (1):
      io_uring/kbuf: check for buffer list readiness after NULL check

Pavel Begunkov (2):
      io_uring: fix mutex_unlock with unreferenced ctx
      io_uring/af_unix: disable sending io_uring over sockets

 io_uring/io_uring.c | 9 +++------
 io_uring/kbuf.c     | 8 ++++----
 io_uring/rsrc.h     | 7 -------
 net/core/scm.c      | 6 ++++++
 4 files changed, 13 insertions(+), 17 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2023-12-08 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 17:48 Jens Axboe [this message]
2023-12-08 20:45 ` [GIT PULL] io_uring fixes for 6.7-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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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