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: 6d07h, last: 6d07h

Sample crash report:
INFO: The task syz-executor:5828 has been waiting for writeback completion for more than 143 seconds.
INFO: The task syz-executor:5828 has been waiting for writeback completion for more than 143 seconds.
INFO: The task syz-executor:5828 has been waiting for writeback completion for more than 143 seconds.
NILFS (loop2): I/O error writing log (start-blocknr=80, block-count=12) in segment 5
NILFS (loop2): I/O error writing log (start-blocknr=80, block-count=12) in segment 5
NILFS (loop2): I/O error writing log (start-blocknr=80, block-count=12) in segment 5
NILFS (loop2): I/O error writing log (start-blocknr=80, block-count=12) in segment 5
NILFS (loop2): disposed unprocessed dirty file(s) when stopping log writer
Buffer I/O error on dev loop2, logical block 0, lost sync page write
NILFS (loop2): unable to write superblock: err=-5
Buffer I/O error on dev loop2, logical block 511, lost sync page write
NILFS (loop2): unable to write superblock: err=-5

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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.