From: syzbot <syzbot+e7be5be00de0c3c2d782@syzkaller.appspotmail.com>
To: atul.droid@gmail.com, davem@davemloft.net, edumazet@google.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,
rauji.raut@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] BUG: sleeping function called from invalid context in hci_cmd_sync_submit
Date: Sat, 16 Sep 2023 21:59:44 -0700 [thread overview]
Message-ID: <000000000000e6b834060586e462@google.com> (raw)
In-Reply-To: <00000000000011da7605ffa4d289@google.com>
syzbot has bisected this issue to:
commit a13f316e90fdb1fb6df6582e845aa9b3270f3581
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: Tue Jun 27 00:25:06 2023 +0000
Bluetooth: hci_conn: Consolidate code for aborting connections
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10885e54680000
start commit: bd6c11bc43c4 Merge tag 'net-next-6.6' of git://git.kernel...
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=12885e54680000
console output: https://syzkaller.appspot.com/x/log.txt?x=14885e54680000
kernel config: https://syzkaller.appspot.com/x/.config?x=634e05b4025da9da
dashboard link: https://syzkaller.appspot.com/bug?extid=e7be5be00de0c3c2d782
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bd8168680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17f4d048680000
Reported-by: syzbot+e7be5be00de0c3c2d782@syzkaller.appspotmail.com
Fixes: a13f316e90fd ("Bluetooth: hci_conn: Consolidate code for aborting connections")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-17 4:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 8:10 [syzbot] [bluetooth?] BUG: sleeping function called from invalid context in hci_cmd_sync_submit syzbot
2023-09-17 4:59 ` syzbot [this message]
2023-12-15 22:47 ` 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=000000000000e6b834060586e462@google.com \
--to=syzbot+e7be5be00de0c3c2d782@syzkaller.appspotmail.com \
--cc=atul.droid@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=rauji.raut@gmail.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).