diff options
author | 2020-07-02 14:56:22 -0700 | |
---|---|---|
committer | 2020-07-02 14:56:22 -0700 | |
commit | c93493b7cd40c20708e3373a7cc8e8049460d7ce (patch) | |
tree | 72e472420baacf2168d484bbeaf521423115c049 /tools/perf/scripts/python/syscall-counts.py | |
parent | Merge tag 'hyperv-fixes-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux (diff) | |
parent | io_uring: use signal based task_work running (diff) | |
download | linux-dev-c93493b7cd40c20708e3373a7cc8e8049460d7ce.tar.xz linux-dev-c93493b7cd40c20708e3373a7cc8e8049460d7ce.zip |
Merge tag 'io_uring-5.8-2020-07-01' of git://git.kernel.dk/linux-block
Pull io_uring fixes from Jens Axboe:
"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. And 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"
* tag 'io_uring-5.8-2020-07-01' of git://git.kernel.dk/linux-block:
io_uring: use signal based task_work running
task_work: teach task_work_add() to do signal_wake_up()
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions