From: syzbot <syzbot+bafeb834708b1bb750bc@syzkaller.appspotmail.com>
To: bvanassche@acm.org, dsterba@suse.com, hch@lst.de,
hdanton@sina.com, jejb@linux.ibm.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com, ming.lei@redhat.com,
nborisov@suse.com, syzkaller-bugs@googlegroups.com, wqu@suse.com
Subject: Re: [syzbot] INFO: task hung in scsi_remove_host
Date: Mon, 22 Aug 2022 13:47:13 -0700 [thread overview]
Message-ID: <0000000000006d456105e6da8d58@google.com> (raw)
In-Reply-To: <000000000000b5187d05e6c08086@google.com>
syzbot has bisected this issue to:
commit ae643a74ebdb150b004601d0d5fe5a1faba9b04d
Author: Qu Wenruo <wqu@suse.com>
Date: Sun May 22 11:47:48 2022 +0000
btrfs: introduce a data checksum checking helper
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=176ef485080000
start commit: e3f259d33c0e Merge tag 'i2c-for-6.0-rc2' of git://git.kern..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14eef485080000
console output: https://syzkaller.appspot.com/x/log.txt?x=10eef485080000
kernel config: https://syzkaller.appspot.com/x/.config?x=3bd9363f7b80ef9c
dashboard link: https://syzkaller.appspot.com/bug?extid=bafeb834708b1bb750bc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=108e1a3d080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154720f3080000
Reported-by: syzbot+bafeb834708b1bb750bc@syzkaller.appspotmail.com
Fixes: ae643a74ebdb ("btrfs: introduce a data checksum checking helper")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-08-22 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 13:42 [syzbot] INFO: task hung in scsi_remove_host syzbot
2022-08-21 21:21 ` Bart Van Assche
2022-08-22 20:47 ` syzbot [this message]
2022-08-22 21:20 ` Bart Van Assche
2022-08-22 21:01 ` Bart Van Assche
2022-08-22 21:45 ` syzbot
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=0000000000006d456105e6da8d58@google.com \
--to=syzbot+bafeb834708b1bb750bc@syzkaller.appspotmail.com \
--cc=bvanassche@acm.org \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=nborisov@suse.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wqu@suse.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).