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

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: <YsFBU1ZzeTy1lVu4@infradead.org>
Date:   Sun, 3 Jul 2022 00:12:19 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     "Dae R. Jeong" <threeearcat@...il.com>
Cc:     axboe@...nel.dk, rostedt@...dmis.org, mingo@...hat.com,
        linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: INFO: task hung in blk_trace_remove

On Sun, Jul 03, 2022 at 01:57:20PM +0900, Dae R. Jeong wrote:
> Hello,
> 
> We observed an issue "INFO: task hung in blk_trace_remove" during
> fuzzing.
> 
> Unfortunately, we have not found a reproducer for the crash yet. We
> will inform you if we have any update on this crash.
> 
> The crash information is attached at the end of this email.

This looks like it is due to locking an on the /dev/sg node instead
of the more usual (and more tested) block device node.

It might make sense to run with lockdep enabled to get a better
grip on potential locking issues here.