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-final
Date: Fri, 27 Oct 2023 13:53:52 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

Fix for an issue reported where reading fdinfo could find a NULL thread
as we didn't properly synchronize, and then a disable for the
IOCB_DIO_CALLER_COMP optimization as a recent reported highlighted how
that could lead to deadlocks if the task issued async O_DIRECT writes
and then proceeded to do sync fallocate() calls.

Please pull!


The following changes since commit 8b51a3956d44ea6ade962874ade14de9a7d16556:

  io_uring: fix crash with IORING_SETUP_NO_MMAP and invalid SQ ring address (2023-10-18 09:22:14 -0600)

are available in the Git repository at:

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

for you to fetch changes up to 838b35bb6a89c36da07ca39520ec071d9250334d:

  io_uring/rw: disable IOCB_DIO_CALLER_COMP (2023-10-25 08:02:29 -0600)

----------------------------------------------------------------
io_uring-6.6-2023-10-27

----------------------------------------------------------------
Jens Axboe (2):
      io_uring/fdinfo: lock SQ thread while retrieving thread cpu/pid
      io_uring/rw: disable IOCB_DIO_CALLER_COMP

 io_uring/fdinfo.c | 18 ++++++++++++------
 io_uring/rw.c     |  9 ---------
 2 files changed, 12 insertions(+), 15 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2023-10-27 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 19:53 Jens Axboe [this message]
2023-10-28  0:14 ` [GIT PULL] io_uring fixes for 6.6-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 \
    [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