INFO: task kworker/u4:10:4338 blocked for more than 143 seconds. Not tainted 5.15.110-syzkaller #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/u4:10 state:D stack:19040 pid: 4338 ppid: 2 flags:0x00004000 Workqueue: writeback wb_workfn (flush-7:4) Call Trace: context_switch kernel/sched/core.c:5026 [inline] __schedule+0x12c4/0x4590 kernel/sched/core.c:6372 schedule+0x11b/0x1f0 kernel/sched/core.c:6455 rwsem_down_write_slowpath+0xebb/0x15c0 kernel/locking/rwsem.c:1157 __down_write_common kernel/locking/rwsem.c:1284 [inline] __down_write kernel/locking/rwsem.c:1293 [inline] down_write+0x164/0x170 kernel/locking/rwsem.c:1542 f2fs_balance_fs+0x4d4/0x6a0 fs/f2fs/segment.c:529 f2fs_write_inode+0x4c3/0x540 fs/f2fs/inode.c:727 write_inode fs/fs-writeback.c:1475 [inline] __writeback_single_inode+0x644/0xe30 fs/fs-writeback.c:1680 writeback_sb_inodes+0xbf0/0x1a50 fs/fs-writeback.c:1905 __writeback_inodes_wb+0x114/0x400 fs/fs-writeback.c:1976 wb_writeback+0x465/0xc50 fs/fs-writeback.c:2081 wb_check_old_data_flush fs/fs-writeback.c:2181 [inline] wb_do_writeback fs/fs-writeback.c:2234 [inline] wb_workfn+0xc55/0x1130 fs/fs-writeback.c:2263 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306 worker_thread+0xaca/0x1280 kernel/workqueue.c:2453 kthread+0x3f6/0x4f0 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298 Showing all locks held in the system: 1 lock held by khungtaskd/27: #0: ffffffff8c91c4e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30 2 locks held by getty/3261: #0: ffff88814b2de098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252 #1: ffffc900024a42e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147 4 locks held by kworker/u4:10/4338: #0: ffff8881425c4938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279 #1: ffffc9000472fd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281 #2: ffff8881477800e0 (&type->s_umount_key#53){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:418 #3: ffff88801e299108 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x4d4/0x6a0 fs/f2fs/segment.c:529 4 locks held by kworker/u4:16/4769: #0: ffff8881425c4938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279 #1: ffffc90004c0fd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281 #2: ffff88803f19a0e0 (&type->s_umount_key#53){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:418 #3: ffff88802470d108 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x4d4/0x6a0 fs/f2fs/segment.c:529 4 locks held by kworker/u4:12/12808: #0: ffff8881425c4938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2279 #1: ffffc90002e1fd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2281 #2: ffff8880799fe0e0 (&type->s_umount_key#53){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:418 #3: ffff88801d519108 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x4d4/0x6a0 fs/f2fs/segment.c:529 2 locks held by syz-executor.4/16570: 2 locks held by syz-executor.3/16652: 2 locks held by syz-executor.2/16653: ============================================= NMI backtrace for cpu 0 CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.110-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111 nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline] check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline] watchdog+0xe72/0xeb0 kernel/hung_task.c:295 kthread+0x3f6/0x4f0 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298 Sending NMI from CPU 0 to CPUs 1: NMI backtrace for cpu 1 CPU: 1 PID: 16570 Comm: syz-executor.4 Not tainted 5.15.110-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023 RIP: 0010:__get_node_page+0x54b/0x820 fs/f2fs/node.c:1422 Code: 00 00 e8 98 fc 28 fe f0 80 23 fb 4c 89 ff be 01 00 00 00 e8 e7 27 ff ff 4c 89 f0 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f 5d c3 a0 a0 df fd 4c 89 e7 be 01 00 00 00 e8 c3 27 ff ff 4c 63 f3 eb RSP: 0018:ffffc9000502da70 EFLAGS: 00000282 RAX: 0000000000000000 RBX: 00000000fffffffe RCX: ffffffff83a03618 RDX: ffff88802303d700 RSI: 00000000fffffffe RDI: 0000000000000000 RBP: 0000000000000103 R08: ffffffff83a039bd R09: fffff94000407289 R10: 0000000000000000 R11: dffffc0000000001 R12: ffffea0002039440 R13: ffff88801e298000 R14: 0000000000000001 R15: dffffc0000000000 FS: 00007f3c2b6db700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fda6ddadef8 CR3: 0000000019f6d000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: do_read_inode fs/f2fs/inode.c:349 [inline] f2fs_iget+0x61d/0x49c0 fs/f2fs/inode.c:505 gc_data_segment fs/f2fs/gc.c:1476 [inline] do_garbage_collect+0x2821/0x7600 fs/f2fs/gc.c:1670 f2fs_gc+0x9e5/0x1ad0 fs/f2fs/gc.c:1764 f2fs_balance_fs+0x4e8/0x6a0 fs/f2fs/segment.c:530 f2fs_write_single_data_page+0xc2a/0x1830 fs/f2fs/data.c:2866 f2fs_write_cache_pages fs/f2fs/data.c:3079 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3230 [inline] f2fs_write_data_pages+0x17de/0x2c00 fs/f2fs/data.c:3257 do_writepages+0x481/0x730 mm/page-writeback.c:2364 filemap_fdatawrite_wbc+0x1d6/0x230 mm/filemap.c:400 __filemap_fdatawrite_range mm/filemap.c:433 [inline] file_write_and_wait_range+0x1cb/0x2b0 mm/filemap.c:810 f2fs_do_sync_file+0x650/0x19d0 fs/f2fs/file.c:274 generic_write_sync include/linux/fs.h:2913 [inline] f2fs_file_write_iter+0x476/0xb80 fs/f2fs/file.c:4357 __kernel_write+0x5b1/0xa60 fs/read_write.c:539 __dump_emit+0x264/0x3a0 fs/coredump.c:875 dump_user_range+0x91/0x320 fs/coredump.c:949 elf_core_dump+0x3c7d/0x4570 fs/binfmt_elf.c:2285 do_coredump+0x1852/0x31e0 fs/coredump.c:826 get_signal+0xc06/0x14e0 kernel/signal.c:2875 arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:865 handle_signal_work kernel/entry/common.c:148 [inline] exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208 irqentry_exit_to_user_mode+0x5/0x30 kernel/entry/common.c:314 exc_page_fault+0x342/0x740 arch/x86/mm/fault.c:1544 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:568 RIP: 0033:0x0 Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. RSP: 002b:0000000020000188 EFLAGS: 00010217 RAX: 0000000000000000 RBX: 00007f3c2d288f80 RCX: 00007f3c2d169169 RDX: 0000000020000040 RSI: 0000000020000180 RDI: 0000000000000000 RBP: 00007f3c2d1c4ca1 R08: 0000000020000240 R09: 0000000020000240 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc1abbe0cf R14: 00007f3c2b6db300 R15: 0000000000022000