From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: "[email protected]" <[email protected]>,
io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 5.8-rc4
Date: Wed, 1 Jul 2020 22:30:24 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
One fix in here, for a regression in 5.7 where a task is waiting in the
kernel for a condition, but that condition won't become true until
task_work is run. The task_work can't be run exactly because the task is
waiting in the kernel, so we'll never make any progress. One example of
that is registering an eventfd and queueing io_uring work, and then the
task goes and waits in eventfd read with the expectation that it'll get
woken (and read an event) when the io_uring request completes. The
io_uring request is finished through task_work, which won't get run
while the task is looping in eventfd read.
Please pull!
The following changes since commit d60b5fbc1ce8210759b568da49d149b868e7c6d3:
io_uring: fix current->mm NULL dereference on exit (2020-06-25 07:20:43 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/io_uring-5.8-2020-07-01
for you to fetch changes up to ce593a6c480a22acba08795be313c0c6d49dd35d:
io_uring: use signal based task_work running (2020-06-30 12:39:05 -0600)
----------------------------------------------------------------
io_uring-5.8-2020-07-01
----------------------------------------------------------------
Jens Axboe (1):
io_uring: use signal based task_work running
Oleg Nesterov (1):
task_work: teach task_work_add() to do signal_wake_up()
fs/io_uring.c | 32 ++++++++++++++++++++++++--------
include/linux/sched/jobctl.h | 4 +++-
include/linux/task_work.h | 5 ++++-
kernel/signal.c | 10 +++++++---
kernel/task_work.c | 16 ++++++++++++++--
5 files changed, 52 insertions(+), 15 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-07-02 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 4:30 Jens Axboe [this message]
2020-07-02 22:30 ` [GIT PULL] io_uring fixes for 5.8-rc4 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] \
[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