From: syzbot <syzbot+c715e1bd8dfbcb1ab176@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
iulia.tanasescu@nxp.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] [bluetooth?] BUG: sleeping function called from invalid context in __hci_cmd_sync_sk
Date: Wed, 20 Sep 2023 15:54:45 -0700 [thread overview]
Message-ID: <000000000000fd0b980605d242ed@google.com> (raw)
In-Reply-To: <000000000000a91cfe05fe5161f2@google.com>
syzbot has bisected this issue to:
commit 2e846cd83f6285f4fee49389954b1b1215f5e504
Author: Iulia Tanasescu <iulia.tanasescu@nxp.com>
Date: Tue May 30 14:21:59 2023 +0000
Bluetooth: ISO: Add support for connecting multiple BISes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15636364680000
start commit: 1f6ce8392d6f Add linux-next specific files for 20230613
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=17636364680000
console output: https://syzkaller.appspot.com/x/log.txt?x=13636364680000
kernel config: https://syzkaller.appspot.com/x/.config?x=d103d5f9125e9fe9
dashboard link: https://syzkaller.appspot.com/bug?extid=c715e1bd8dfbcb1ab176
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11287563280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14395963280000
Reported-by: syzbot+c715e1bd8dfbcb1ab176@syzkaller.appspotmail.com
Fixes: 2e846cd83f62 ("Bluetooth: ISO: Add support for connecting multiple BISes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-09-20 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 11:12 [syzbot] [bluetooth?] BUG: sleeping function called from invalid context in __hci_cmd_sync_sk syzbot
2023-09-20 22:54 ` syzbot [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=000000000000fd0b980605d242ed@google.com \
--to=syzbot+c715e1bd8dfbcb1ab176@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=iulia.tanasescu@nxp.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 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).