WARNING: possible circular locking dependency detected (3)

Status: closed as invalid on 2017/10/02 13:49
First crash: 3315d, last: 3315d
▶ ▼ 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 3317d 3317d 0/29 closed as invalid on 2017/09/30 06:49
android-414 WARNING: possible circular locking dependency detected -1 syz, C 8 2580d 2759d 0/1 public: reported C repro on 2019/04/10 16:14
upstream WARNING: possible circular locking dependency detected (5) -1 syz, C 1 410d 410d 29/29 fixed on 2025/10/29 21:02
upstream WARNING: possible circular locking dependency detected (4) net -1 syz, C 27 3108d 3115d 8/29 fixed on 2018/07/09 18:05
upstream WARNING: possible circular locking dependency detected -1 1 3327d 3327d 0/29 closed as invalid on 2017/09/24 05:49

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
4.14.0-rc3+ #22 Not tainted
------------------------serialport: VM disconnected.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2017/10/02 12:28 upstream 9e66317d3c92 c26ea367 .config console log report ci-upstream-kasan-gce-386
* Struck through repros no longer work on HEAD.