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.6-rc5
Date: Fri, 6 Oct 2023 10:36:02 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

A few fixes for the 6.6 kernel release:

- syzbot report on a crash on 32-bit arm with highmem, and went digging
  to check for potentially similar issues and found one more (me)

- Fix a syzbot report with PROVE_LOCKING=y and setting up the ring in a
  disabled state (me)

- Fix for race with CPU hotplut and io-wq init (Jeff)

Please pull!


  io_uring/fs: remove sqe->rw_flags checking from LINKAT (2023-09-29 03:07:09 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/io_uring-6.6-2023-10-06

for you to fetch changes up to 0f8baa3c9802fbfe313c901e1598397b61b91ada:

  io-wq: fully initialize wqe before calling cpuhp_state_add_instance_nocalls() (2023-10-05 14:11:18 -0600)

----------------------------------------------------------------
io_uring-6.6-2023-10-06

----------------------------------------------------------------
Jeff Moyer (1):
      io-wq: fully initialize wqe before calling cpuhp_state_add_instance_nocalls()

Jens Axboe (3):
      io_uring/kbuf: don't allow registered buffer rings on highmem pages
      io_uring: ensure io_lockdep_assert_cq_locked() handles disabled rings
      io_uring: don't allow IORING_SETUP_NO_MMAP rings on highmem pages

 io_uring/io-wq.c    | 10 ++++------
 io_uring/io_uring.c | 16 +++++++++++++++-
 io_uring/io_uring.h | 41 +++++++++++++++++++++++++++--------------
 io_uring/kbuf.c     | 27 +++++++++++++++++++--------
 4 files changed, 65 insertions(+), 29 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2023-10-06 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06 16:36 Jens Axboe [this message]
2023-10-06 22:51 ` [GIT PULL] io_uring fixes for 6.6-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