INFO: The task syz.NUM.NUM:LINE has been waiting for writeback completion for more than NUM seconds. (2)

Status: moderation: reported on 2026/08/06 06:18
Labels: prio:normal
[Documentation on labels]
Reported-by: syzbot+925fede3fbcac6581bee@syzkaller.appspotmail.com
First crash: 4d20h, last: 4d20h
▶ ▼ ✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
e2d15113 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ✅ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ INFO: The task syz.NUM.NUM:LINE has been waiting for writeback completion for more than NUM seconds. (2) 2026/08/04 00:51 2026/08/04 00:51 2026/08/04 00:55 cb1adeae
▶ ▼ Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: The task syz.NUM.NUM:LINE has been waiting for writeback completion for more than NUM seconds. -1 syz 44 166d 242d 0/29 auto-obsoleted due to no activity on 2026/05/02 16:17

Sample crash report:
INFO: The task syz.0.6:4898 has been waiting for writeback completion for more than 141 seconds.
EXT4-fs (loop0): unmounting filesystem 00000000-0000-0000-0000-000000000000.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/02 06:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e2d5e23967d0 e611ffe1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: The task syz.NUM.NUM:LINE has been waiting for writeback completion for more than NUM seconds.
* Struck through repros no longer work on HEAD.