diff options
| author | Jens Axboe <axboe@kernel.dk> | 2026-11-15 08:12:06 -0700 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2026-11-15 08:20:58 -0700 |
| commit | d4912d6440bf6d255e1fa1c360c8ddb39d0e01bd (patch) | |
| tree | 2c8ecd753b0a890f1964bc4477111a00a5bef270 /rust | |
| parent | 4d3db66c5363dcf42c3d43ebaea330ac2d1888bb (diff) | |
io_uring/io-wq: show stuck workers rather than WARN on a slow exit
io_wq_exit_workers() triggers a WARN_ON_ONCE() if it has waited more than
IO_URING_EXIT_WAIT_MAX for the workers to exit. That can be triggered at
will, for example with an open on a FUSE mount where the server never
replies to the lookup. The worker can't be canceled, and the exit waits
until the server goes away.
The stack trace from the WARN isn't useful either, as it's that of the
exiting task and that is always the task exit, exec, or SQPOLL thread
exit path. Print a message and show the workers that are still around
instead, that's where the interesting stack traces are.
Reported-by: syzbot+b0d54b9e81de55179e47@syzkaller.appspotmail.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'rust')
0 files changed, 0 insertions, 0 deletions
