From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] Followup io_uring fixes for 5.16-rc3
Date: Sat, 27 Nov 2021 09:04:37 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
The locking fixup that was applied earlier this rc has both a deadlock
and IRQ safety issue, let's get that ironed out before -rc3. This pull
request contains:
- Link traversal locking fix (Pavel)
- Cancelation fix (Pavel)
- Relocate cond_resched() for huge buffer chain freeing, avoiding a
softlockup warning (Ye)
- Fix timespec validation (Ye)
Please pull!
The following changes since commit 674ee8e1b4a41d2fdffc885c55350c3fbb38c22a:
io_uring: correct link-list traversal locking (2021-11-22 19:31:54 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/io_uring-5.16-2021-11-27
for you to fetch changes up to f6223ff799666235a80d05f8137b73e5580077b9:
io_uring: Fix undefined-behaviour in io_issue_sqe (2021-11-27 06:41:38 -0700)
----------------------------------------------------------------
io_uring-5.16-2021-11-27
----------------------------------------------------------------
Pavel Begunkov (2):
io_uring: fail cancellation for EXITING tasks
io_uring: fix link traversal locking
Ye Bin (2):
io_uring: fix soft lockup when call __io_remove_buffers
io_uring: Fix undefined-behaviour in io_issue_sqe
fs/io_uring.c | 73 ++++++++++++++++++++++++++++++++++++++++-------------------
1 file changed, 50 insertions(+), 23 deletions(-)
--
Jens Axboe
next reply other threads:[~2021-11-27 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 16:04 Jens Axboe [this message]
2021-11-27 19:47 ` [GIT PULL] Followup io_uring fixes for 5.16-rc3 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