On 10/17/23 14:23, Bob Pearson wrote:
Not really, but stuck could mean it died (no threads active) or it is in a loop or waiting to be scheduled. It looks dead. The lower layers are waiting to get kicked into action by some event but it hasn't happened. This is conjecture on my part though.
This call stack means that I/O has been submitted by the block layer and that it did not get completed. Which I/O request got stuck can be verified by e.g. running the list-pending-block-requests script that I posted some time ago. See also https://lore.kernel.org/all/55c0fe61-a091-b351-11b4-fa7f668e49d7@xxxxxxx/. Thanks, Bart.
