From: syzbot <syzbot+b825d87fe2d043e3e652@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, fgheet255t@gmail.com,
hdanton@sina.com, johan.hedberg@gmail.com,
josephsih@chromium.org, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
lrh2000@pku.edu.cn, luiz.dentz@gmail.com,
luiz.von.dentz@intel.com, marcel@holtmann.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, yinghsu@chromium.org
Subject: Re: [syzbot] [bluetooth?] possible deadlock in sco_conn_del
Date: Fri, 16 Jun 2023 08:09:29 -0700 [thread overview]
Message-ID: <00000000000051087405fe4092cc@google.com> (raw)
In-Reply-To: <00000000000098289005dc17b71b@google.com>
syzbot suspects this issue was fixed by commit:
commit a2ac591cb4d83e1f2d4b4adb3c14b2c79764650a
Author: Ruihan Li <lrh2000@pku.edu.cn>
Date: Wed May 3 13:39:36 2023 +0000
Bluetooth: Fix UAF in hci_conn_hash_flush again
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13755717280000
start commit: e4cf7c25bae5 Merge tag 'kbuild-fixes-v6.2' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=555d27e379d75ff1
dashboard link: https://syzkaller.appspot.com/bug?extid=b825d87fe2d043e3e652
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10052058480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1190687c480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: Fix UAF in hci_conn_hash_flush again
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-06-16 15:09 UTC|newest]
Thread overview: 5+ 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
2023-06-16 15:09 ` syzbot [this message]
2023-06-19 6:10 ` [syzbot] [bluetooth?] " Dmitry Vyukov
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=00000000000051087405fe4092cc@google.com \
--to=syzbot+b825d87fe2d043e3e652@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fgheet255t@gmail.com \
--cc=hdanton@sina.com \
--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=lrh2000@pku.edu.cn \
--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 \
--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 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).