syzbot


INFO: The task syz-executor:NUM has been waiting for writeback completion for more than NUM seconds.

Status: moderation: reported on 2026/01/07 00:08
Reported-by: syzbot+9aa5b9a263c658890082@syzkaller.appspotmail.com
First crash: 63d, last: 6d20h

Sample crash report:
INFO: The task syz-executor:5799 has been waiting for writeback completion for more than 141 seconds.
INFO: The task syz-executor:5799 has been waiting for writeback completion for more than 141 seconds.
XFS (loop4): Unmounting Filesystem 9f1cad42-11bd-4e12-8f0b-f07876b81d9a
XFS (loop4): Uncorrected metadata errors detected; please run xfs_repair.

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/02/28 15:39 upstream 4d349ee5c778 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: The task syz-executor:NUM has been waiting for writeback completion for more than NUM seconds.
2026/01/31 05:20 upstream 283073725700 e01a0ca6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: The task syz-executor:NUM has been waiting for writeback completion for more than NUM seconds.
2026/01/02 18:51 linux-next cc3aa43b44bd d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: The task syz-executor:NUM has been waiting for writeback completion for more than NUM seconds.
* Struck through repros no longer work on HEAD.