Re: INFO: task hung in lo_release

From: Tetsuo Handa
Date: Fri Nov 02 2018 - 21:06:38 EST


On 2018/11/03 4:24, Dmitry Vyukov wrote:
>> Dmitry, it is impossible to check what these lock holders are doing without dump of these threads
>> (they are not always TASK_UNINTERRUPTIBLE waiters; e.g. PID=18508 is TASK_RUNNING with a lock held).
>
> I know. One day I will hopefully get to implementing dump collection...
>
>> Jens, when can we start testing "[PATCH v3] block/loop: Serialize ioctl operations." ?
>
> Was that merged? If we have a potential fix, merging it may be the
> simplest way to address it without debugging.
> I see that this "[v4] block/loop: Serialize ioctl operations." still
> has "State: New":
> https://patchwork.kernel.org/patch/10612217/
>

Jan Kara is going to resend https://marc.info/?i=20181010100415.26525-1-jack@xxxxxxx
after the merge window closes.