linux-kernel - Re: INFO: task hung in lo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <c3f63c2f-f163-d626-f96e-9e274b037124@i-love.sakura.ne.jp>
Date:   Sat, 3 Nov 2018 10:06:05 +0900
From:   Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     Jens Axboe <axboe@...nel.dk>,
        syzbot <syzbot+a4e4a2663a21c3c3c2b1@...kaller.appspotmail.com>,
        linux-block@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Jan Kara <jack@...e.cz>
Subject: Re: INFO: task hung in lo_release

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@suse.cz
after the merge window closes.