From: syzbot <syzbot+list513be271df212c03ceba@syzkaller.appspotmail.com>
To: johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly bluetooth report (Aug 2023)
Date: Tue, 01 Aug 2023 05:53:54 -0700 [thread overview]
Message-ID: <0000000000001981210601dc0aa5@google.com> (raw)
Hello bluetooth maintainers/developers,
This is a 31-day syzbot report for the bluetooth subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/bluetooth
During the period, 1 new issues were detected and 1 were fixed.
In total, 23 issues are still open and 54 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 8070 Yes possible deadlock in rfcomm_sk_state_change
https://syzkaller.appspot.com/bug?extid=d7ce59b06b3eb14fd218
<2> 4315 Yes WARNING in hci_conn_timeout
https://syzkaller.appspot.com/bug?extid=2446dd3cb07277388db6
<3> 1974 Yes possible deadlock in rfcomm_dlc_exists
https://syzkaller.appspot.com/bug?extid=b69a625d06e8ece26415
<4> 875 Yes BUG: sleeping function called from invalid context in hci_cmd_sync_submit
https://syzkaller.appspot.com/bug?extid=e7be5be00de0c3c2d782
<5> 151 Yes WARNING in call_timer_fn
https://syzkaller.appspot.com/bug?extid=6fb78d577e89e69602f9
<6> 84 No possible deadlock in hci_unregister_dev
https://syzkaller.appspot.com/bug?extid=c933391d8e4089f1f53e
<7> 51 No possible deadlock in discov_off
https://syzkaller.appspot.com/bug?extid=f047480b1e906b46a3f4
<8> 4 No KASAN: slab-use-after-free Write in sco_conn_del
https://syzkaller.appspot.com/bug?extid=6b9277cad941daf126a2
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2023-08-01 12:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0000000000001981210601dc0aa5@google.com \
--to=syzbot+list513be271df212c03ceba@syzkaller.appspotmail.com \
--cc=johan.hedberg@gmail.com \
--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=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).