Description
In the Linux kernel, the following vulnerability has been resolved: io_uring: wait interruptibly for request completions on exit WHen the ring exits, cleanup is done and the final cancelation and waiting on completions is done by io_ring_exit_work. That function is invoked by kworker, which doesn't take any signals. Because of that, it doesn't really matter if we wait for completions in TASK_INTERRUPTIBLE or TASK_UNINTERRUPTIBLE state. However, it does matter to the hung task detection checker! Normally we expect cancelations and completions to happen rather quickly. Some test cases, however, will exit the ring and park the owning task stopped (eg via SIGSTOP). If the owning task needs to run task_work to complete requests, then io_ring_exit_work won't make any progress until the task is runnable again. Hence io_ring_exit_work can trigger the hung task detection, which is particularly problematic if panic-on-hung-task is enabled. As the ring exit doesn't take signals to begin with, have it wait interruptibly rather than uninterruptibly. io_uring has a separate stuck-exit warning that triggers independently anyway, so we're not really missing anything by making this switch.
Product status
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 28e649dc9947e6525c95e32aa9a8e147925e3f56
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 8e29835366138389bfad3b31ea06960d0a77bf77
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before b50d6e06cca7b67a3d73ca660dda27662b76e6ea
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 58e80cb68b057e974768792c34708c6957810486
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 4826c59453b3b4677d6bf72814e7ababdea86949
5.10.188
5.15.121
6.1.39
6.4.4
6.5
References
git.kernel.org/...c/28e649dc9947e6525c95e32aa9a8e147925e3f56
git.kernel.org/...c/8e29835366138389bfad3b31ea06960d0a77bf77
git.kernel.org/...c/b50d6e06cca7b67a3d73ca660dda27662b76e6ea
git.kernel.org/...c/58e80cb68b057e974768792c34708c6957810486
git.kernel.org/...c/4826c59453b3b4677d6bf72814e7ababdea86949
