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, 2 new issues were detected and 1 were fixed. In total, 20 issues are still open and 55 have been fixed so far. Some of the still happening issues: Ref Crashes Repro Title <1> 8940 Yes possible deadlock in rfcomm_sk_state_change https://syzkaller.appspot.com/bug?extid=d7ce59b06b3eb14fd218 <2> 4685 Yes WARNING in hci_conn_timeout https://syzkaller.appspot.com/bug?extid=2446dd3cb07277388db6 <3> 2847 Yes possible deadlock in rfcomm_dlc_exists https://syzkaller.appspot.com/bug?extid=b69a625d06e8ece26415 <4> 1418 Yes BUG: sleeping function called from invalid context in hci_cmd_sync_submit https://syzkaller.appspot.com/bug?extid=e7be5be00de0c3c2d782 <5> 1064 Yes INFO: task can't die in __lock_sock https://syzkaller.appspot.com/bug?extid=7d51f807c81b190a127d <6> 224 Yes WARNING in call_timer_fn https://syzkaller.appspot.com/bug?extid=6fb78d577e89e69602f9 <7> 90 No possible deadlock in hci_unregister_dev https://syzkaller.appspot.com/bug?extid=c933391d8e4089f1f53e <8> 65 Yes KASAN: slab-use-after-free Read in hci_send_acl https://syzkaller.appspot.com/bug?extid=a0c80b06ae2cb8895bc4 <9> 57 No possible deadlock in discov_off https://syzkaller.appspot.com/bug?extid=f047480b1e906b46a3f4 <10> 8 Yes BUG: sleeping function called from invalid context in __hci_cmd_sync_sk https://syzkaller.appspot.com/bug?extid=c715e1bd8dfbcb1ab176 --- 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@xxxxxxxxxxxxxxxx. 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.
