F2FS-fs (loop0): Try to recover 1th superblock, ret: 0 F2FS-fs (loop0): Mounted with checkpoint version = 48b305e5 ====================================================== WARNING: possible circular locking dependency detected 6.1.44-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor126/4216 is trying to acquire lock: ffff0000df3990a8 (&fi->i_xattr_sem){.+.+}-{3:3}, at: f2fs_down_read fs/f2fs/f2fs.h:2154 [inline] ffff0000df3990a8 (&fi->i_xattr_sem){.+.+}-{3:3}, at: f2fs_getxattr+0xa4/0x1198 fs/f2fs/xattr.c:531 but task is already holding lock: ffff0000df3d16f8 (&fi->i_sem){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2179 [inline] ffff0000df3d16f8 (&fi->i_sem){+.+.}-{3:3}, at: f2fs_do_tmpfile+0x30/0x198 fs/f2fs/dir.c:869 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&fi->i_sem){+.+.}-{3:3}: down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 f2fs_down_write fs/f2fs/f2fs.h:2179 [inline] f2fs_add_inline_entry+0x350/0x650 fs/f2fs/inline.c:645 f2fs_add_dentry fs/f2fs/dir.c:815 [inline] f2fs_do_add_link+0x2c4/0x5a4 fs/f2fs/dir.c:858 f2fs_add_link fs/f2fs/f2fs.h:3530 [inline] f2fs_create+0x634/0x8b4 fs/f2fs/namei.c:367 lookup_open fs/namei.c:3413 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0xeac/0x2548 fs/namei.c:3711 do_filp_open+0x1bc/0x3cc fs/namei.c:3741 do_sys_openat2+0x128/0x3d8 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __arm64_sys_openat+0x1f0/0x240 fs/open.c:1345 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581 -> #0 (&fi->i_xattr_sem){.+.+}-{3:3}: check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x3338/0x764c kernel/locking/lockdep.c:5056 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669 down_read+0x64/0x308 kernel/locking/rwsem.c:1520 f2fs_down_read fs/f2fs/f2fs.h:2154 [inline] f2fs_getxattr+0xa4/0x1198 fs/f2fs/xattr.c:531 __f2fs_get_acl+0x6c/0x5e4 fs/f2fs/acl.c:179 f2fs_acl_create fs/f2fs/acl.c:375 [inline] f2fs_init_acl+0xe8/0x8e8 fs/f2fs/acl.c:418 f2fs_init_inode_metadata+0x8a8/0x11e8 fs/f2fs/dir.c:587 f2fs_do_tmpfile+0x44/0x198 fs/f2fs/dir.c:870 __f2fs_tmpfile+0x1d4/0x33c fs/f2fs/namei.c:874 f2fs_get_tmpfile+0x40/0x54 fs/f2fs/namei.c:943 f2fs_ioc_start_atomic_write fs/f2fs/file.c:2107 [inline] __f2fs_ioctl+0x8240/0xb4b0 fs/f2fs/file.c:4171 f2fs_ioctl+0x130/0x1a0 fs/f2fs/file.c:4261 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&fi->i_sem); lock(&fi->i_xattr_sem); lock(&fi->i_sem); lock(&fi->i_xattr_sem); *** DEADLOCK *** 5 locks held by syz-executor126/4216: #0: ffff0000d4f6e460 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write_file+0x64/0x1e8 fs/namespace.c:437 #1: ffff0000df3d0a38 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline] #1: ffff0000df3d0a38 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: f2fs_ioc_start_atomic_write fs/f2fs/file.c:2068 [inline] #1: ffff0000df3d0a38 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: __f2fs_ioctl+0x3b80/0xb4b0 fs/f2fs/file.c:4171 #2: ffff0000df3d1010 (&fi->i_gc_rwsem[WRITE]){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2179 [inline] #2: ffff0000df3d1010 (&fi->i_gc_rwsem[WRITE]){+.+.}-{3:3}, at: f2fs_ioc_start_atomic_write fs/f2fs/file.c:2082 [inline] #2: ffff0000df3d1010 (&fi->i_gc_rwsem[WRITE]){+.+.}-{3:3}, at: __f2fs_ioctl+0x4de4/0xb4b0 fs/f2fs/file.c:4171 #3: ffff0000d79283b0 (&sbi->cp_rwsem){.+.+}-{3:3}, at: f2fs_down_read fs/f2fs/f2fs.h:2154 [inline] #3: ffff0000d79283b0 (&sbi->cp_rwsem){.+.+}-{3:3}, at: f2fs_lock_op fs/f2fs/f2fs.h:2197 [inline] #3: ffff0000d79283b0 (&sbi->cp_rwsem){.+.+}-{3:3}, at: __f2fs_tmpfile+0x1a4/0x33c fs/f2fs/namei.c:869 #4: ffff0000df3d16f8 (&fi->i_sem){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2179 [inline] #4: ffff0000df3d16f8 (&fi->i_sem){+.+.}-{3:3}, at: f2fs_do_tmpfile+0x30/0x198 fs/f2fs/dir.c:869 stack backtrace: CPU: 1 PID: 4216 Comm: syz-executor126 Not tainted 6.1.44-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023 Call trace: dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106 dump_stack+0x1c/0x58 lib/dump_stack.c:113 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2056 check_noncircular+0x2cc/0x378 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x3338/0x764c kernel/locking/lockdep.c:5056 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669 down_read+0x64/0x308 kernel/locking/rwsem.c:1520 f2fs_down_read fs/f2fs/f2fs.h:2154 [inline] f2fs_getxattr+0xa4/0x1198 fs/f2fs/xattr.c:531 __f2fs_get_acl+0x6c/0x5e4 fs/f2fs/acl.c:179 f2fs_acl_create fs/f2fs/acl.c:375 [inline] f2fs_init_acl+0xe8/0x8e8 fs/f2fs/acl.c:418 f2fs_init_inode_metadata+0x8a8/0x11e8 fs/f2fs/dir.c:587 f2fs_do_tmpfile+0x44/0x198 fs/f2fs/dir.c:870 __f2fs_tmpfile+0x1d4/0x33c fs/f2fs/namei.c:874 f2fs_get_tmpfile+0x40/0x54 fs/f2fs/namei.c:943 f2fs_ioc_start_atomic_write fs/f2fs/file.c:2107 [inline] __f2fs_ioctl+0x8240/0xb4b0 fs/f2fs/file.c:4171 f2fs_ioctl+0x130/0x1a0 fs/f2fs/file.c:4261 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581