syzbot


possible deadlock in corrupted

Status: upstream: reported C repro on 2022/06/06 17:18
Reported-by: syzbot+5c3c53e6db862466e7b6@syzkaller.appspotmail.com
First crash: 22d, last: 2d03h

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

Sample crash report:
=====================================================
WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
5.19.0-rc3-syzkaller-00043-g3abc3ae553c7 #0 Not tainted
-----------------------------------------------------
syz-executor298/3612 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
ffffffff8c80a058 (tasklist_lock){.+.+}-{2:2}, at: send_sigio+0xbe/0x300 fs/fcntl.c:791

and this task is already holding:
ffff888021360130 (&f->f_owner.lock){....}-{2:2}, at: send_sigio+0x2f/0x300 fs/fcntl.c:777
which would create a new lock dependency:
 (&f->f_owner.lock){....}-{2:2} -> (tasklist_lock){.+.+}-{2:2}

but this new dependency connects a HARDIRQ-irq-safe lock:
 (&timer->lock){-...}-{2:2}


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