Re: INFO: task hung in blkdev_open bug
- To: yang lan <lanyang0908@gmail.com>
- Cc: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org, josef@toxicpanda.com, linux-block@vger.kernel.org, nbd@other.debian.org, syzkaller-bugs@googlegroups.com, linux-fsdevel@vger.kernel.org, axboe@kernel.dk, haris.iqbal@ionos.com, jinpu.wang@ionos.com, brauner@kernel.org
- Subject: Re: INFO: task hung in blkdev_open bug
- From: Matthew Wilcox <willy@infradead.org>
- Date: Wed, 17 May 2023 13:20:24 +0100
- Message-id: <[🔎] ZGTGiNItObrI2Z34@casper.infradead.org>
- In-reply-to: <CAAehj2=HQDk-AMYpVR7i91hbQC4G5ULKd9iYoP05u_9tay8VMw@mail.gmail.com>
- References: <CAAehj2=HQDk-AMYpVR7i91hbQC4G5ULKd9iYoP05u_9tay8VMw@mail.gmail.com>
On Wed, May 17, 2023 at 07:12:23PM +0800, yang lan wrote:
> root@syzkaller:~# 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@syzkaller:~# 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
Reply to: