From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.10-rc4
Date: Fri, 14 Jun 2024 10:06:19 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Two fixes from Pavel headed to stable:
- Ensure that the task state is correct before attempting to grab a
mutex
- Split cancel sequence flag into a separate variable, as it can get set
by someone not owning the request (but holding the ctx lock)
Please pull!
The following changes since commit 73254a297c2dd094abec7c9efee32455ae875bdf:
io_uring: fix possible deadlock in io_register_iowq_max_workers() (2024-06-04 07:39:17 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.10-20240614
for you to fetch changes up to f4a1254f2a076afb0edd473589bf40f9b4d36b41:
io_uring: fix cancellation overwriting req->flags (2024-06-13 19:25:28 -0600)
----------------------------------------------------------------
io_uring-6.10-20240614
----------------------------------------------------------------
Pavel Begunkov (2):
io_uring/rsrc: don't lock while !TASK_RUNNING
io_uring: fix cancellation overwriting req->flags
include/linux/io_uring_types.h | 3 ++-
io_uring/cancel.h | 4 ++--
io_uring/io_uring.c | 1 +
io_uring/rsrc.c | 1 +
4 files changed, 6 insertions(+), 3 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-06-14 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 16:06 Jens Axboe [this message]
2024-06-14 18:29 ` [GIT PULL] io_uring fixes for 6.10-rc4 Linus Torvalds
2024-06-15 0:22 ` Jens Axboe
2024-06-15 0:39 ` Jens Axboe
2024-06-14 18:52 ` 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