From: syzbot <syzbot+b825d87fe2d043e3e652@syzkaller.appspotmail.com>
To: davem@davemloft.net, johan.hedberg@gmail.com,
josephsih@chromium.org, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, yinghsu@chromium.org
Subject: Re: [syzbot] possible deadlock in sco_conn_del
Date: Mon, 11 Apr 2022 14:48:09 -0700 [thread overview]
Message-ID: <00000000000072fb2705dc67e6c0@google.com> (raw)
In-Reply-To: <00000000000098289005dc17b71b@google.com>
syzbot has bisected this issue to:
commit 92b8aa6d18f7a9ae36a0f71d31742aeef201207a
Author: Ying Hsu <yinghsu@chromium.org>
Date: Sat Mar 26 07:09:28 2022 +0000
Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10fada04f00000
start commit: d12d7e1cfe38 Add linux-next specific files for 20220411
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=12fada04f00000
console output: https://syzkaller.appspot.com/x/log.txt?x=14fada04f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=58fcaf7d8df169a6
dashboard link: https://syzkaller.appspot.com/bug?extid=b825d87fe2d043e3e652
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16a2ff0f700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149fd2df700000
Reported-by: syzbot+b825d87fe2d043e3e652@syzkaller.appspotmail.com
Fixes: 92b8aa6d18f7 ("Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-04-11 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 22:08 [syzbot] possible deadlock in sco_conn_del syzbot
2022-04-11 18:51 ` syzbot
2022-04-11 21:48 ` syzbot [this message]
2023-06-16 15:09 ` [syzbot] [bluetooth?] " syzbot
2023-06-19 6:10 ` Dmitry Vyukov
[not found] <20220411232710.6167-1-hdanton@sina.com>
2022-04-11 23:37 ` [syzbot] " syzbot
[not found] <20220412015446.6243-1-hdanton@sina.com>
2022-04-12 2:07 ` 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=00000000000072fb2705dc67e6c0@google.com \
--to=syzbot+b825d87fe2d043e3e652@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=josephsih@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yinghsu@chromium.org \
/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.