syzbot


possible deadlock in pipe_lock (4)
Status: auto-closed as invalid on 2021/07/03 13:02
Reported-by: syzbot+86cae0697c35c6294c32@syzkaller.appspotmail.com
First crash: 177d, last: 177d
similar bugs (8):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in pipe_lock 50806 1410d 1458d 0/22 closed as invalid on 2018/02/14 14:20
upstream possible deadlock in pipe_lock (2) 3 921d 990d 0/22 auto-closed as invalid on 2019/10/18 15:02
linux-4.19 possible deadlock in pipe_lock (2) C 10 27d 672d 0/1 upstream: reported C repro on 2019/12/26 07:17
upstream possible deadlock in pipe_lock (5) C done 5 96d 95d 21/22 upstream: reported C repro on 2021/07/24 19:07
android-49 possible deadlock in pipe_lock 5 735d 928d 0/3 auto-closed as invalid on 2020/02/21 12:40
linux-4.19 possible deadlock in pipe_lock C done 2 914d 917d 1/1 fixed on 2019/11/29 10:34
android-44 possible deadlock in pipe_lock C 82 695d 928d 0/2 public: reported C repro on 2019/04/14 08:51
upstream possible deadlock in pipe_lock (3) C inconclusive done 4 634d 671d 17/22 fixed on 2020/08/18 22:40

Sample crash report:

Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-linux-next-kasan-gce-root 2021/05/04 13:01 linux-next 9a9aa07ae18b 09efdd63 .config log report info possible deadlock in pipe_lock