From: syzbot <syzbot+e68a3899a8927b14f863@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
marcel@holtmann.org, netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: task hung in hci_dev_do_open (2)
Date: Tue, 21 Jun 2022 21:37:08 -0700 [thread overview]
Message-ID: <000000000000cacae905e201e3be@google.com> (raw)
In-Reply-To: <000000000000cf2ece05def394c8@google.com>
syzbot has bisected this issue to:
commit d0b137062b2de75b264b84143d21c98abc5f5ad2
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: Wed Oct 27 23:58:59 2021 +0000
Bluetooth: hci_sync: Rework init stages
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1376c63ff00000
start commit: 38a288f5941e Add linux-next specific files for 20220506
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10f6c63ff00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1776c63ff00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f4fbf50aa82985b
dashboard link: https://syzkaller.appspot.com/bug?extid=e68a3899a8927b14f863
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=111555fef00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1629b3eaf00000
Reported-by: syzbot+e68a3899a8927b14f863@syzkaller.appspotmail.com
Fixes: d0b137062b2d ("Bluetooth: hci_sync: Rework init stages")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-06-22 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 7:17 [syzbot] INFO: task hung in hci_dev_do_open (2) syzbot
2022-06-22 4:37 ` syzbot [this message]
[not found] <20220514081824.1035-1-hdanton@sina.com>
2022-05-14 8:31 ` syzbot
[not found] <20220514110016.1193-1-hdanton@sina.com>
2022-05-14 11:40 ` 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=000000000000cacae905e201e3be@google.com \
--to=syzbot+e68a3899a8927b14f863@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.