From: syzbot <syzbot+217e3f1283cafe80586e@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.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?] INFO: task hung in hci_cmd_sync_clear (3)
Date: Thu, 26 Dec 2024 05:05:02 -0800 [thread overview]
Message-ID: <676d547e.050a0220.226966.0084.GAE@google.com> (raw)
In-Reply-To: <672efa7e.050a0220.138bd5.0039.GAE@google.com>
syzbot has bisected this issue to:
commit a0bfde167b506423111ddb8cd71930497a40fc54
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=11845adf980000
start commit: 0a9b9d17f3a7 Merge tag 'pm-6.12-rc8' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=13845adf980000
console output: https://syzkaller.appspot.com/x/log.txt?x=15845adf980000
kernel config: https://syzkaller.appspot.com/x/.config?x=327b6119dd928cbc
dashboard link: https://syzkaller.appspot.com/bug?extid=217e3f1283cafe80586e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1094e1a7980000
Reported-by: syzbot+217e3f1283cafe80586e@syzkaller.appspotmail.com
Fixes: a0bfde167b50 ("Bluetooth: ISO: Add support for connecting multiple BISes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-12-26 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 6:00 [syzbot] [bluetooth?] INFO: task hung in hci_cmd_sync_clear (3) syzbot
2024-12-26 13:05 ` syzbot [this message]
2025-02-03 13:12 ` [syzbot] " syzbot
[not found] <20250203131206.7852-1-iulia.tanasescu@nxp.com>
2025-02-03 15:29 ` 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=676d547e.050a0220.226966.0084.GAE@google.com \
--to=syzbot+217e3f1283cafe80586e@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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 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.