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

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 17 May 2023 13:20:24 +0100
From:   Matthew Wilcox <willy@...radead.org>
To:     yang lan <lanyang0908@...il.com>
Cc:     viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org,
        josef@...icpanda.com, linux-block@...r.kernel.org,
        nbd@...er.debian.org, syzkaller-bugs@...glegroups.com,
        linux-fsdevel@...r.kernel.org, axboe@...nel.dk,
        haris.iqbal@...os.com, jinpu.wang@...os.com, brauner@...nel.org
Subject: Re: INFO: task hung in blkdev_open bug

On Wed, May 17, 2023 at 07:12:23PM +0800, yang lan wrote:
> root@...kaller:~# uname -a
> Linux syzkaller 5.10.179 #1 SMP PREEMPT Thu Apr 27 16:22:48 CST 2023

Does this reproduce on current kernels, eg 6.4-rc2?

> root@...kaller:~# gcc poc_blkdev.c -o poc_blkdev

You need to include poc_blkdev.c as part of your report.

> Please let me know if I can provide any more information, and I hope I
> didn't mess up this bug report.

I suspect you've done something that is known to not work (as root,
so we won't necessarily care).  But I can't really say without seeing
what you've done.  Running syzkaller is an art, and most people aren't
good at it.  It takes a lot of work to submit good quality bug reports,
see this article:

https://blog.regehr.org/archives/2037