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 fix for 6.7-rc2
Date: Fri, 17 Nov 2023 10:41:23 -0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

Just a single fixup for a change we made in this release, which caused a
regression in sometimes missing fdinfo output if the SQPOLL thread had
the lock held when fdinfo output was retrieved. This brings us back on
par with what we had before, where just the main uring_lock will prevent
that output. We'd love to get rid of that too, but that is beyond the
scope of this release and will have to wait for 6.8.

Please pull!


The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:

  Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)

are available in the Git repository at:

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

for you to fetch changes up to a0d45c3f596be53c1bd8822a1984532d14fdcea9:

  io_uring/fdinfo: remove need for sqpoll lock for thread/pid retrieval (2023-11-15 06:35:46 -0700)

----------------------------------------------------------------
io_uring-6.7-2023-11-17

----------------------------------------------------------------
Jens Axboe (1):
      io_uring/fdinfo: remove need for sqpoll lock for thread/pid retrieval

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

-- 
Jens Axboe


             reply	other threads:[~2023-11-17 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 17:41 Jens Axboe [this message]
2023-11-17 22:16 ` [GIT PULL] io_uring fix for 6.7-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 \
    [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