Avoid spurious syzbot induced hung task panics
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | io_uring: add IO_URING_EXIT_WAIT_MAX definitionio_uring/ io_uring/ | +7 | 0 replies | |
| 2/2 | io_uring/io-wq: don't trigger hung task for syzbot crazinessio_uring/ | +21 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCHSET 0/2] Avoid spurious syzbot induced hung task panics
Hi,
For details, see this saga:
https://lore.kernel.org/io-uring/[email protected]/
where the tldr is that there's no real bug here, it's just syzbot doing hundreds of 2GB /dev/msr* reads in a tiny vm and with a bunch of debugging enabled. That leads to triggering the hung task detector when we wait on io-wq workers to exit. I did queue a patch for 6.19 that makes this less likely to occur, as it'll only run the very first of the items before noticing the cancelation:
https://lore.kernel.org/io-uring/[email protected]/
but even that isn't quite enough due to how much syzbot overloads the system.
This will still throw a WARN_ON_ONCE(), which perhaps should just be a printk() of some sort as the trace isn't THAT interesting. But it will avoid hitting the hung task timeout detector, which for syzbot leads to a panic + reboot.
io_uring/io-wq.c | 22 +++++++++++++++++++++- io_uring/io_uring.c | 2 +- io_uring/io_uring.h | 6 ++++++ 3 files changed, 28 insertions(+), 2 deletions(-)
Signature · 1 line
Jens Axboe