fix task_work interation with freezing
Status from this message: Applied, thanks!
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest2 patches 2 repliesApplied
- v22 patches 3 repliesSuperseded
- v12 patches 17 repliesSuperseded
Patches in v3 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | io_uring/io-wq: limit retrying worker initialisationio_uring/ | +7 | 0 replies | |
| 2/2 | kernel: rerun task_work while freezing in get_signal()kernel/ | +8 | 1 reply |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Oleg Nesterov | Tejun Heo |
|---|---|---|
| 1/2 | ||
| 2/2 | A-b | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v3 0/2] fix task_work interation with freezing
It's reported [1] that a task_work queued at a wrong time can prevent freezing and make the tasks to spin in get_signal() taking 100% of CPU. Patch 1 is a preparation. Patch 2 addresses the issue.
[1] https://github.com/systemd/systemd/issues/33626
v3: Slightly adjust commit messages
v2: Move task_work_run() into do_freezer_trap()
Correct the Fixes tag is 2/2
Pavel Begunkov (2):
io_uring/io-wq: limit retrying worker initialisation
kernel: rerun task_work while freezing in get_signal()
io_uring/io-wq.c | 10 +++++++--- kernel/signal.c | 8 ++++++++ 2 files changed, 15 insertions(+), 3 deletions(-)
Signature · 1 line
2.44.0