From: Jens Axboe <[email protected]>
To: io-uring <[email protected]>
Cc: Linus Torvalds <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.1-rc6
Date: Fri, 25 Nov 2022 17:19:01 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
A few fixes that should go into this release:
- A few poll related fixes. One fixing a race condition between poll
cancelation and trigger, and one making the overflow handling a bit
more robust (Lin, Pavel)
- Fix an fput() for error handling in the direct file table (Lin)
- Fix for a regression introduced in this cycle, where we don't always
get TIF_NOTIFY_SIGNAL cleared appropriately (me)
Please pull!
The following changes since commit 7fdbc5f014c3f71bc44673a2d6c5bb2d12d45f25:
io_uring: disallow self-propelled ring polling (2022-11-18 09:29:31 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.1-2022-11-25
for you to fetch changes up to 7cfe7a09489c1cefee7181e07b5f2bcbaebd9f41:
io_uring: clear TIF_NOTIFY_SIGNAL if set and task_work not available (2022-11-25 10:55:08 -0700)
----------------------------------------------------------------
io_uring-6.1-2022-11-25
----------------------------------------------------------------
Jens Axboe (1):
io_uring: clear TIF_NOTIFY_SIGNAL if set and task_work not available
Lin Ma (2):
io_uring/filetable: fix file reference underflow
io_uring/poll: fix poll_refs race with cancelation
Pavel Begunkov (2):
io_uring: cmpxchg for poll arm refs release
io_uring: make poll refs more robust
io_uring/filetable.c | 2 --
io_uring/io_uring.h | 9 +++++++--
io_uring/poll.c | 47 ++++++++++++++++++++++++++++++++++++++++-------
3 files changed, 47 insertions(+), 11 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-11-26 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 0:19 Jens Axboe [this message]
2022-11-26 2:25 ` [GIT PULL] io_uring fixes for 6.1-rc6 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-11-18 22:43 Jens Axboe
2022-11-19 1:24 ` 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