INFO: task hung in ext4_buffered_write_iter (4)

Status: auto-obsoleted due to no activity on 2026/10/25 22:44
Subsystems: ext4
Labels: prio:high
[Documentation on labels]
First crash: 115d, last: 115d
▶ ▼ ✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
5a404ef3 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ✅ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ✅ VMHostTrigger: ❌ ❓ INFO: task hung in ext4_buffered_write_iter (4) 2026/07/29 01:46 2026/07/29 01:46 2026/07/29 02:21 7be3c40b
▶ ▼ Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in ext4_buffered_write_iter (3) ext4 1 1 1202d 1202d 0/29 auto-obsoleted due to no activity on 2023/11/04 07:21
upstream INFO: task hung in ext4_buffered_write_iter ext4 1 1 2255d 2255d 0/29 auto-closed as invalid on 2020/12/15 19:03
upstream INFO: task hung in ext4_buffered_write_iter (2) ext4 1 24 1302d 1497d 0/29 auto-obsoleted due to no activity on 2023/07/27 13:19

Sample crash report:
INFO: task syz.3.108:5233 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.108       state:D stack:0     pid:5233  tgid:5223  ppid:4718   task_flags:0x400040 flags:0x00000001
Call trace:
 __switch_to+0x2b0/0x6e0 arch/arm64/kernel/process.c:775 (T)
 context_switch kernel/sched/core.c:5510 [inline]
 __schedule+0x1370/0x2d80 kernel/sched/core.c:7234
 __schedule_loop kernel/sched/core.c:7311 [inline]
 schedule+0x13c/0x20c kernel/sched/core.c:7326
 schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:7383
 rwsem_down_write_slowpath+0x6ec/0x1174 kernel/locking/rwsem.c:1215
 __down_write_common kernel/locking/rwsem.c:1347 [inline]
 __down_write kernel/locking/rwsem.c:1356 [inline]
 down_write+0xb4/0xc0 kernel/locking/rwsem.c:1632
 inode_lock include/linux/fs.h:1024 [inline]
 ext4_buffered_write_iter+0xa0/0x2ec fs/ext4/file.c:311
 ext4_file_write_iter+0x1dc/0x134c fs/ext4/file.c:-1
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x51c/0xa0c fs/read_write.c:687
 ksys_pwrite64+0x118/0x1ac fs/read_write.c:794
 __do_sys_pwrite64 fs/read_write.c:802 [inline]
 __se_sys_pwrite64 fs/read_write.c:799 [inline]
 __arm64_sys_pwrite64+0xa0/0xb8 fs/read_write.c:799
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
 el0_svc+0x64/0x260 arch/arm64/kernel/entry-common.c:736
 el0t_64_sync_handler+0x48/0x148 arch/arm64/kernel/entry-common.c:755
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:594

Showing all locks held in the system:
3 locks held by kworker/u8:1/15:
 #0: ffff0000c004c140 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff0000c004c140 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x734/0x10b8 kernel/workqueue.c:3405
 #1: ffff80008ec87c40 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffff80008ec87c40 ((linkwatch_work).work){+.+.}-{0:0}, at: process_scheduled_works+0x73c/0x10b8 kernel/workqueue.c:3405
 #2: ffff800089dd3780 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:80
1 lock held by khungtaskd/31:
 #0: ffff800088cf6fe0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffff800088cf6fe0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:840 [inline]
 #0: ffff800088cf6fe0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x4c/0x188 kernel/locking/lockdep.c:6775
2 locks held by getty/4493:
 #0: ffff0000cffab0a0 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
 #1: ffff8000924cb2e8 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x348/0xf78 drivers/tty/n_tty.c:2211
5 locks held by syz.3.108/5224:
1 lock held by syz.3.108/5229:
2 locks held by syz.3.108/5233:
 #0: ffff0000dbd26450 (sb_writers#3){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2733 [inline]
 #0: ffff0000dbd26450 (sb_writers#3){.+.+}-{0:0}, at: vfs_write+0x248/0xa0c fs/read_write.c:683
 #1: ffff0000f2dd4520 (&sb->s_type->i_mutex_key#10){++++}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
 #1: ffff0000f2dd4520 (&sb->s_type->i_mutex_key#10){++++}-{4:4}, at: ext4_buffered_write_iter+0xa0/0x2ec fs/ext4/file.c:311
2 locks held by syz.1.373/6345:
 #0: ffff0000c14bb5f8 (&sb->s_type->i_mutex_key#9){++++}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
 #0: ffff0000c14bb5f8 (&sb->s_type->i_mutex_key#9){++++}-{4:4}, at: blkdev_fallocate+0x208/0x354 block/fops.c:882
 #1: ffff0000c14bb790 (mapping.invalidate_lock){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1079 [inline]
 #1: ffff0000c14bb790 (mapping.invalidate_lock){++++}-{4:4}, at: blkdev_fallocate+0x22c/0x354 block/fops.c:883
2 locks held by syz.8.1015/8810:
2 locks held by syz.7.1016/8812:

=============================================


Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/07/27 22:35 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 365f9c7a6b81 4cb2b096 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in ext4_buffered_write_iter
* Struck through repros no longer work on HEAD.