[v5.15] INFO: task hung in f2fs_issue_checkpoint

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9465fef4ae35 Linux 5.15.153
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17b8abfd180000
kernel config: https://syzkaller.appspot.com/x/.config?x=74ff83133fa97f6c
dashboard link: https://syzkaller.appspot.com/bug?extid=d685021e4fad21571354
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3c82fda40b43/disk-9465fef4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ec13893dc103/vmlinux-9465fef4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7b44910e5283/Image-9465fef4.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d68502...@syzkaller.appspotmail.com

INFO: task syz-executor.3:6487 blocked for more than 143 seconds.
Not tainted 5.15.153-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack: 0 pid: 6487 ppid: 3989 flags:0x0000000d
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6376
schedule+0x11c/0x1c8 kernel/sched/core.c:6459
schedule_timeout+0xb8/0x344 kernel/time/timer.c:1860
do_wait_for_common+0x214/0x388 kernel/sched/completion.c:85
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x4c/0x64 kernel/sched/completion.c:138
f2fs_issue_checkpoint+0x240/0x3c0
f2fs_sync_fs+0x1c0/0x4e8 fs/f2fs/super.c:1678
f2fs_cross_rename fs/f2fs/namei.c:1272 [inline]
f2fs_rename2+0x1390/0x2004 fs/f2fs/namei.c:1308
vfs_rename+0xac8/0xe04 fs/namei.c:4832
do_renameat2+0xa00/0x10c0 fs/namei.c:4985
__do_sys_renameat2 fs/namei.c:5018 [inline]
__se_sys_renameat2 fs/namei.c:5015 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffff800014ae14a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:311
2 locks held by kworker/u4:1/136:
3 locks held by kworker/u4:3/153:
#0: ffff0000c21c8138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001a887c00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
#2: ffff0000c11000e0 (&type->s_umount_key#58){++++}-{3:3}, at: trylock_super+0x28/0xf8 fs/super.c:418
3 locks held by kworker/u4:5/1342:
#0: ffff0000c21c8138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001cd77c00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
#2: ffff0000f5dea0e0 (&type->s_umount_key#58){++++}-{3:3}, at: trylock_super+0x28/0xf8 fs/super.c:418
1 lock held by udevd/3582:
2 locks held by getty/3717:
#0: ffff0000d2eeb098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff800018e462e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1204 drivers/tty/n_tty.c:2158
2 locks held by kworker/0:10/4097:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001d557c00 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
3 locks held by kworker/u4:6/4203:
#0: ffff0000c038c138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001f837c00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
#2: ffff8000169ef850 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf4/0x9bc net/core/net_namespace.c:558
2 locks held by kworker/0:14/4258:
#0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001fa07c00 ((work_completion)(&map->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
3 locks held by kworker/u4:8/4377:
#0: ffff0000c21c8138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2283
#1: ffff80001f187c00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2285
#2: ffff0000f0b580e0 (&type->s_umount_key#58){++++}-{3:3}, at: trylock_super+0x28/0xf8 fs/super.c:418
3 locks held by kworker/u4:13/4391:
3 locks held by syz-executor.3/6487:
#0: ffff0000f0b58460 (sb_writers#19){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
#1: ffff0000eedb9450 (&type->i_mutex_dir_key#11/1){+.+.}-{3:3}, at: do_renameat2+0x534/0x10c0 fs/namei.c:4924
#2: ffff0000eedb9dd0 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
#2: ffff0000eedb9dd0 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: vfs_rename+0x68c/0xe04 fs/namei.c:4797
3 locks held by f2fs_ckpt-7:3/6546:
3 locks held by syz-executor.2/6588:
#0: ffff0000f5dea460 (sb_writers#19){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
#1: ffff0000eedbc3d0 (&type->i_mutex_dir_key#11/1){+.+.}-{3:3}, at: do_renameat2+0x534/0x10c0 fs/namei.c:4924
#2: ffff0000eedbcd50 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
#2: ffff0000eedbcd50 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: vfs_rename+0x68c/0xe04 fs/namei.c:4797
3 locks held by f2fs_ckpt-7:2/6656:
3 locks held by syz-executor.1/6855:
#0: ffff0000c1100460 (sb_writers#19){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
#1: ffff0000def93a50 (&type->i_mutex_dir_key#11/1){+.+.}-{3:3}, at: do_renameat2+0x534/0x10c0 fs/namei.c:4924
#2: ffff0000eedbd6d0 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
#2: ffff0000eedbd6d0 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: vfs_rename+0x68c/0xe04 fs/namei.c:4797
2 locks held by f2fs_ckpt-7:1/6902:
2 locks held by syz-executor.4/7910:
#0: ffff0000cbf35118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xe0/0x6b0 block/bdev.c:912
#1: ffff0000cbf0e468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa8/0x9b8 drivers/block/loop.c:1365
2 locks held by syz-executor.0/8286:
#0: ffff0000cbe8b118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xe0/0x6b0 block/bdev.c:912
#1: ffff0000cbe7a468 (&lo->lo_mutex){+.+.}-{3:3}, at: lo_release+0x58/0x210 drivers/block/loop.c:2070
2 locks held by syz-executor.1/8288:

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



---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup