syzbot


INFO: task hung in f2fs_file_write_iter

Status: auto-obsoleted due to no activity on 2023/09/06 20:28
Subsystems: f2fs
[Documentation on labels]
First crash: 501d, last: 405d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in f2fs_file_write_iter f2fs 5 502d 605d 0/1 upstream: reported on 2022/11/20 07:00
upstream INFO: task hung in f2fs_file_write_iter (2) f2fs 1 244d 244d 0/27 auto-obsoleted due to no activity on 2024/02/14 19:21

Sample crash report:
INFO: task syz-executor.5:7929 blocked for more than 143 seconds.
      Not tainted 6.4.0-rc5-syzkaller-00024-g5f63595ebd82 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5  state:D stack:24096 pid:7929  ppid:5026   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0x187b/0x4900 kernel/sched/core.c:6669
 schedule+0xc3/0x180 kernel/sched/core.c:6745
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6804
 rwsem_down_write_slowpath+0xedd/0x13a0 kernel/locking/rwsem.c:1178
 __down_write_common+0x1aa/0x200 kernel/locking/rwsem.c:1306
 inode_lock include/linux/fs.h:775 [inline]
 f2fs_file_write_iter+0x29d/0x2520 fs/f2fs/file.c:4700
 call_write_iter include/linux/fs.h:1868 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x790/0xb20 fs/read_write.c:584
 ksys_write+0x1a0/0x2c0 fs/read_write.c:637
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc605a8c169
RSP: 002b:00007fc606758168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fc605babf80 RCX: 00007fc605a8c169
RDX: 0000000000000078 RSI: 0000000020000280 RDI: 0000000000000007
RBP: 00007fc605ae7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc2b716aaf R14: 00007fc606758300 R15: 0000000000022000
 </TASK>
INFO: task syz-executor.5:7973 blocked for more than 143 seconds.
      Not tainted 6.4.0-rc5-syzkaller-00024-g5f63595ebd82 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5  state:D stack:29528 pid:7973  ppid:5026   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0x187b/0x4900 kernel/sched/core.c:6669
 schedule+0xc3/0x180 kernel/sched/core.c:6745
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6804
 __mutex_lock_common+0xe33/0x2530 kernel/locking/mutex.c:679
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
 __fdget_pos+0x254/0x2f0 fs/file.c:1047
 fdget_pos include/linux/file.h:73 [inline]
 ksys_write+0x82/0x2c0 fs/read_write.c:628
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc605a8c169
RSP: 002b:00007fc606716168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fc605bac120 RCX: 00007fc605a8c169
RDX: 0000000000000078 RSI: 0000000020000280 RDI: 0000000000000007
RBP: 00007fc605ae7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc2b716aaf R14: 00007fc606716300 R15: 0000000000022000
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8cf276f0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:518
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8cf27ab0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:518
1 lock held by khungtaskd/28:
 #0: ffffffff8cf27520 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
4 locks held by kworker/u4:3/52:
 #0: ffff888012a8d938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc90000bd7d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
 #2: ffff888029ece0e0 (&type->s_umount_key#61){++++}-{3:3}, at: trylock_super+0x1f/0xf0 fs/super.c:414
 #3: ffff88801fb2d2a8 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2112 [inline]
 #3: ffff88801fb2d2a8 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x51a/0x6f0 fs/f2fs/segment.c:435
3 locks held by kworker/0:2/901:
 #0: ffff888012470d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x77e/0x10e0 kernel/workqueue.c:2378
 #1: ffffc900046dfd20 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x7c8/0x10e0 kernel/workqueue.c:2380
 #2: 
ffff888078360240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x2d1/0x4130 drivers/net/netdevsim/fib.c:1489
2 locks held by getty/4744:
 #0: 
ffff88802ca12098
 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015b02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6ab/0x1db0 drivers/tty/n_tty.c:2176
3 locks held by syz-executor.5/7929:
 #0: ffff888076e60fe8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x254/0x2f0 fs/file.c:1047
 #1: ffff888029ece460 (sb_writers#18){.+.+}-{0:0}, at: vfs_write+0x223/0xb20 fs/read_write.c:580
 #2: ffff88807574d0e8 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
 #2: ffff88807574d0e8 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: f2fs_file_write_iter+0x29d/0x2520 fs/f2fs/file.c:4700
4 locks held by syz-executor.5/7930:
1 lock held by syz-executor.5/7973:
 #0: ffff888076e60fe8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x254/0x2f0 fs/file.c:1047
2 locks held by syz-executor.5/8838:
 #0: ffff888029ece0e0 (&type->s_umount_key#61){++++}-{3:3}, at: iterate_supers+0xb0/0x1e0 fs/super.c:743
 #1: ffff88801ef7a7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline]
 #1: ffff88801ef7a7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inodes_sb+0x278/0xab0 fs/fs-writeback.c:2728
2 locks held by syz-executor.5/9049:
 #0: ffff888029ece0e0 (&type->s_umount_key#61){++++}-{3:3}, at: iterate_supers+0xb0/0x1e0 fs/super.c:743
 #1: ffff88801ef7a7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline]
 #1: ffff88801ef7a7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inodes_sb+0x278/0xab0 fs/fs-writeback.c:2728

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.4.0-rc5-syzkaller-00024-g5f63595ebd82 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x498/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x187/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xec2/0xf00 kernel/hung_task.c:379
 kthread+0x2b8/0x350 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 9030 Comm: syz-executor.5 Not tainted 6.4.0-rc5-syzkaller-00024-g5f63595ebd82 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:112 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:128 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:159 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:178 [inline]
RIP: 0010:kasan_check_range+0x14e/0x290 mm/kasan/generic.c:187
Code: 85 e2 00 00 00 41 83 ff 02 74 14 48 bd 06 00 00 00 00 fc ff df 80 3c 2b 00 0f 85 c8 00 00 00 bb 08 00 00 00 44 29 fb 49 01 d9 <4d> 29 ce 4c 89 f5 48 8d 5d 07 48 85 ed 48 0f 49 dd 48 c1 eb 03 85
RSP: 0018:ffffc90017f6fd58 EFLAGS: 00000296
RAX: 1ffff92002fedf01 RBX: 0000000000000004 RCX: ffffffff8154136e
RDX: 0000000000000001 RSI: 0000000000000090 RDI: ffffc90017f6fde0
RBP: dffffc0000000003 R08: dffffc0000000000 R09: fffff52002fedfc0
R10: 1ffff92002fedfcd R11: dffffc0000000001 R12: 1ffff92002fedfb8
R13: 0000000040000001 R14: fffff52002fedfce R15: 0000000000000004
FS:  000055555728d400(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe5bb566fc0 CR3: 0000000039993000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 __asan_memset+0x23/0x40 mm/kasan/shadow.c:84
 __do_sys_wait4 kernel/exit.c:1807 [inline]
 __se_sys_wait4 kernel/exit.c:1804 [inline]
 __x64_sys_wait4+0x10e/0x1e0 kernel/exit.c:1804
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fe5ba889d47
Code: 89 7c 24 10 48 89 4c 24 18 e8 f5 58 02 00 4c 8b 54 24 18 8b 54 24 14 41 89 c0 48 8b 74 24 08 8b 7c 24 10 b8 3d 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 89 44 24 10 e8 25 59 02 00 8b 44
RSP: 002b:00007ffdefc27a00 EFLAGS: 00000293 ORIG_RAX: 000000000000003d
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fe5ba889d47
RDX: 0000000040000001 RSI: 00007ffdefc27a8c RDI: 00000000ffffffff
RBP: 00007ffdefc27a8c R08: 0000000000000000 R09: 0000000000000010
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 00000000000764a3 R14: 0000000000000005 R15: 00007ffdefc27af0
 </TASK>

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/06/08 20:22 upstream 5f63595ebd82 058b3a5a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_file_write_iter
2023/04/24 10:38 upstream 457391b03803 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_file_write_iter
2023/04/23 05:56 upstream 2caeeb9d4a1b 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_file_write_iter
2023/04/22 09:54 upstream 8e41e0a57566 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_file_write_iter
2023/03/04 05:17 upstream 0a3f9a6b0265 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_file_write_iter
* Struck through repros no longer work on HEAD.