From: syzbot <syzbot+lista37ea1d82518ef3e82b4@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
Date: Wed, 29 Mar 2023 03:03:46 -0700 [thread overview]
Message-ID: <0000000000008a040605f80717b3@google.com> (raw)
Hello bluetooth maintainers/developers,
This is a 30-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 0 were fixed.
In total, 30 issues are still open and 47 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
5798 Yes possible deadlock in rfcomm_sk_state_change
https://syzkaller.appspot.com/bug?extid=d7ce59b06b3eb14fd218
2690 Yes WARNING in hci_conn_timeout
https://syzkaller.appspot.com/bug?extid=2446dd3cb07277388db6
1046 Yes INFO: task can't die in __lock_sock
https://syzkaller.appspot.com/bug?extid=7d51f807c81b190a127d
272 Yes possible deadlock in sco_conn_del
https://syzkaller.appspot.com/bug?extid=b825d87fe2d043e3e652
182 No KASAN: slab-use-after-free Read in hci_conn_hash_flush
https://syzkaller.appspot.com/bug?extid=8bb72f86fc823817bc5d
111 No possible deadlock in rfcomm_dlc_exists
https://syzkaller.appspot.com/bug?extid=b69a625d06e8ece26415
45 Yes WARNING in call_timer_fn
https://syzkaller.appspot.com/bug?extid=6fb78d577e89e69602f9
18 Yes WARNING: ODEBUG bug in put_device
https://syzkaller.appspot.com/bug?extid=a9290936c6e87b3dc3c2
---
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.
reply other threads:[~2023-03-29 10:03 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=0000000000008a040605f80717b3@google.com \
--to=syzbot+lista37ea1d82518ef3e82b4@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 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.