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-rc4
Date: Fri, 1 Dec 2023 11:56:29 -0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

Random assortment of fixes, either heading to stable or fixing an issue
introduced in this series.

- Fix an issue with discontig page checking for IORING_SETUP_NO_MMAP

- Fix an issue with not allowing IORING_SETUP_NO_MMAP also disallowing
  mmap'ed buffer rings

- Fix an issue with deferred release of memory mapped pages

- Fix a lockdep issue with IORING_SETUP_NO_MMAP

- Use fget/fput consistently, even from our sync system calls. No real
  issue here, but if we were ever to allow closing io_uring descriptors
  it would be required. Let's play it safe and just use the full ref
  counted versions upfront. Most uses of io_uring are threaded anyway,
  and hence already doing the full version underneath.

Please pull!


The following changes since commit d6fef34ee4d102be448146f24caf96d7b4a05401:

  io_uring: fix off-by one bvec index (2023-11-20 15:21:38 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/io_uring-6.7-2023-11-30

for you to fetch changes up to 73363c262d6a7d26063da96610f61baf69a70f7c:

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

----------------------------------------------------------------
io_uring-6.7-2023-11-30

----------------------------------------------------------------
Jens Axboe (8):
      io_uring: don't allow discontig pages for IORING_SETUP_NO_MMAP
      io_uring: don't guard IORING_OFF_PBUF_RING with SETUP_NO_MMAP
      io_uring: enable io_mem_alloc/free to be used in other parts
      io_uring/kbuf: defer release of mapped buffer rings
      io_uring/kbuf: recycle freed mapped buffer ring entries
      io_uring/kbuf: prune deferred locked cache when tearing down
      io_uring: free io_buffer_list entries via RCU
      io_uring: use fget/fput consistently

 include/linux/io_uring_types.h |   3 +
 io_uring/cancel.c              |  11 +--
 io_uring/io_uring.c            |  95 ++++++++++++----------
 io_uring/io_uring.h            |   3 +
 io_uring/kbuf.c                | 177 ++++++++++++++++++++++++++++++++++++-----
 io_uring/kbuf.h                |   5 ++
 6 files changed, 224 insertions(+), 70 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2023-12-01 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 18:56 Jens Axboe [this message]
2023-12-01 21:49 ` [GIT PULL] io_uring fixes for 6.7-rc4 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