possible deadlock in corrupted

Status: upstream: reported C repro on 2022/06/06 17:18
First crash: 370d, last: 349d

Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: possible deadlock in input_event (log)
Repro: C syz .config

Fix bisection: fixed by (bisect log) :
commit f856373e2f31ffd340e47e2b00027bd4070f74b3
Author: Felix Fietkau <>
Date: Tue May 31 19:08:24 2022 +0000

  wifi: mac80211: do not wake queues on a vif that is being stopped

Discussions (1)
Title Replies (including bot) Last reply
[syzbot] possible deadlock in corrupted 0 (2) 2022/07/23 11:12
Last patch testing requests (5)
Created Duration User Patch Repo Result
2023/04/21 19:06 19m retest repro upstream report log
2023/04/13 03:11 19m retest repro upstream OK log
2023/01/09 11:32 14m retest repro upstream report log
2022/10/11 23:30 18m retest repro upstream error
2022/10/01 08:30 10m retest repro upstream report log

Sample crash report:
WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
5.18.0-syzkaller-11972-gd1dc87763f40 #0 Not tainted
syz-executor227/3609 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
ffff88801b5aa0c0 (&new->fa_lock){....}-{2:2}, at: 

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Manager Title
2022/06/02 17:07 upstream d1dc87763f40 5783034f .config strace log report syz C ci-upstream-kasan-gce possible deadlock in corrupted
2022/06/23 07:48 upstream 3abc3ae553c7 912f5df7 .config strace log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in corrupted
* Struck through repros no longer work on HEAD.