syzbot


possible deadlock in shmem_fallocate (3)
Status: auto-closed as invalid on 2019/11/05 02:34
Reported-by: syzbot+5d04068d02b9da8a0947@syzkaller.appspotmail.com
First crash: 867d, last: 867d
similar bugs (7):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 possible deadlock in shmem_fallocate (2) 2 613d 681d 0/1 auto-closed as invalid on 2020/09/14 02:25
upstream possible deadlock in shmem_fallocate 8087 1554d 1598d 0/22 closed as invalid on 2017/11/05 09:38
linux-4.19 possible deadlock in shmem_fallocate 1 903d 903d 0/1 auto-closed as invalid on 2019/11/29 05:22
android-49 possible deadlock in shmem_fallocate C 2441 778d 1015d 0/3 public: reported C repro on 2019/04/11 08:44
android-414 possible deadlock in shmem_fallocate C 7876 778d 1015d 0/1 public: reported C repro on 2019/04/11 00:00
upstream possible deadlock in shmem_fallocate (4) C done 81 540d 755d 17/22 fixed on 2020/09/16 22:51
upstream possible deadlock in shmem_fallocate (2) C 1325 1050d 1258d 12/22 fixed on 2019/03/28 12:00

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 2019/09/06 02:33 linux-next 6d028043b55e 040fda58 .config log report