From: syzbot <syzbot+c55f7bc8d4809b2bad59@syzkaller.appspotmail.com>
To: hdanton@sina.com, iam@sung-woo.kim, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
marcel@holtmann.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] possible deadlock in hci_dev_do_close (2)
Date: Mon, 29 Apr 2024 11:37:03 -0700 [thread overview]
Message-ID: <0000000000002d7a7f0617408af1@google.com> (raw)
In-Reply-To: <0000000000007e812306170008d1@google.com>
syzbot has bisected this issue to:
commit 37dd04e4d59487c928bf3561e4bd3a045762eabc
Author: Sungwoo Kim <iam@sung-woo.kim>
Date: Thu Apr 25 04:11:28 2024 +0000
Bluetooth: HCI: fix slab-use-after-free in cmd_sync_work
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14457fd8980000
start commit: bb7a2467e6be Add linux-next specific files for 20240426
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=16457fd8980000
console output: https://syzkaller.appspot.com/x/log.txt?x=12457fd8980000
kernel config: https://syzkaller.appspot.com/x/.config?x=5c6a0288262dd108
dashboard link: https://syzkaller.appspot.com/bug?extid=c55f7bc8d4809b2bad59
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1590bcf8980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1349ee9b180000
Reported-by: syzbot+c55f7bc8d4809b2bad59@syzkaller.appspotmail.com
Fixes: 37dd04e4d594 ("Bluetooth: HCI: fix slab-use-after-free in cmd_sync_work")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-04-29 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 13:39 [syzbot] [bluetooth?] possible deadlock in hci_dev_do_close (2) syzbot
2024-04-28 22:35 ` syzbot
2024-04-28 23:42 ` Hillf Danton
2024-04-29 1:10 ` syzbot
2024-04-29 18:37 ` 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=0000000000002d7a7f0617408af1@google.com \
--to=syzbot+c55f7bc8d4809b2bad59@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=iam@sung-woo.kim \
--cc=johan.hedberg@gmail.com \
--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=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).