syzbot


INFO: task hung in f2fs_write_inode

Status: upstream: reported C repro on 2026/01/23 14:26
Subsystems: f2fs
[Documentation on labels]
Reported-by: syzbot+ffb43ecff88cb2a47dd3@syzkaller.appspotmail.com
First crash: 21d, last: 21d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [f2fs?] INFO: task hung in f2fs_write_inode 0 (1) 2026/01/23 14:26
Last patch testing requests (1)
Created Duration User Patch Repo Result
2026/02/02 14:27 1h27m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci error

Sample crash report:
INFO: task kworker/u8:14:4087 blocked for more than 143 seconds.
Call trace:
 f2fs_write_inode+0x3b0/0x68c fs/f2fs/inode.c:826
 kthread+0x5fc/0x75c kernel/kthread.c:463
 #0: ffff0000c1ff2948 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x63c/0x1558 kernel/workqueue.c:3231
3 locks held by syz-executor142/6594:

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/01/19 14:21 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 59e4d31a0470 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-gce-arm64 INFO: task hung in f2fs_write_inode
* Struck through repros no longer work on HEAD.