diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2021-03-21 12:25:54 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2021-03-21 12:25:54 -0700 |
| commit | 2c41fab1c60b02626c8153a1806a7a1e5d62aaf1 (patch) | |
| tree | f13c693ef22d4fd7b181846c0a45f0a4cea9943e /scripts/gcc-plugins/cyc_complexity_plugin.c | |
| parent | 1d4345eb51a185b2ecd11834dbddca79cb922eb5 (diff) | |
| parent | 0031275d119efe16711cd93519b595e6f9b4b330 (diff) | |
Merge tag 'io_uring-5.12-2021-03-21' of git://git.kernel.dk/linux-block
Pull io_uring followup fixes from Jens Axboe:
- The SIGSTOP change from Eric, so we properly ignore that for
PF_IO_WORKER threads.
- Disallow sending signals to PF_IO_WORKER threads in general, we're
not interested in having them funnel back to the io_uring owning
task.
- Stable fix from Stefan, ensuring we properly break links for short
send/sendmsg recv/recvmsg if MSG_WAITALL is set.
- Catch and loop when needing to run task_work before a PF_IO_WORKER
threads goes to sleep.
* tag 'io_uring-5.12-2021-03-21' of git://git.kernel.dk/linux-block:
io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with MSG_WAITALL
io-wq: ensure task is running before processing task_work
signal: don't allow STOP on PF_IO_WORKER threads
signal: don't allow sending any signals to PF_IO_WORKER threads
Diffstat (limited to 'scripts/gcc-plugins/cyc_complexity_plugin.c')
0 files changed, 0 insertions, 0 deletions