From: Christoph Hellwig <hch@lst.de>
To: Hillf Danton <hdanton@sina.com>
Cc: syzbot <syzbot+0fe7752e52337864d29b@syzkaller.appspotmail.com>,
axboe@kernel.dk, hare@suse.de, hch@lst.de, jack@suse.cz,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: task hung in del_gendisk
Date: Mon, 12 Jul 2021 08:22:41 +0200 [thread overview]
Message-ID: <20210712062241.GA9697@lst.de> (raw)
In-Reply-To: <20210712041417.835-1-hdanton@sina.com>
On Mon, Jul 12, 2021 at 12:14:17PM +0800, Hillf Danton wrote:
> Fix it by s/nbd->destroy_complete/&nbd->destroy_complete/
>
> Note this isnt a cure to what the syzbot reported.
Yeah. The completion stuff does look bogus, but the actual sysbot
report is about the fact that del_gendisk is called from ->release.
prev parent reply other threads:[~2021-07-12 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 15:55 [syzbot] INFO: task hung in del_gendisk syzbot
[not found] ` <20210712041417.835-1-hdanton@sina.com>
2021-07-12 6:22 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210712062241.GA9697@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+0fe7752e52337864d29b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).