syzbot

 sign-in | mailing list | source | docs
🐞 Open [1483]
≡ Subsystems
🐞 Fixed [6786]
🐞 Invalid [17524]
⬇ Missing Backports [221]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
💬 Send us feedback

WARNING: possible circular locking dependency detected (5)

Status: fixed on 2025/10/29 21:02
Fix commit: 9f7c02e03157 nbd: restrict sockets to TCP and UDP
First crash: 87d, last: 87d
▶ ▼ Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING: possible circular locking dependency detected (2) -1 1 2995d 2995d 0/29 closed as invalid on 2017/09/30 06:49
android-414 WARNING: possible circular locking dependency detected -1 C 8 2258d 2437d 0/1 public: reported C repro on 2019/04/10 16:14
upstream WARNING: possible circular locking dependency detected (4) net -1 C 27 2785d 2793d 8/29 fixed on 2018/07/09 18:05
upstream WARNING: possible circular locking dependency detected -1 1 3005d 3005d 0/29 closed as invalid on 2017/09/24 05:49
upstream WARNING: possible circular locking dependency detected (3) -1 1 2992d 2992d 0/29 closed as invalid on 2017/10/02 13:49

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/15 12:05 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8736259279a3 e2beed91 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 WARNING: possible circular locking dependency detected
* Struck through repros no longer work on HEAD.