F2FS-fs (loop2): Try to recover 1th superblock, ret: 0 F2FS-fs (loop2): Mounted with checkpoint version = 753bd00b ====================================================== WARNING: possible circular locking dependency detected 6.1.53-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/15150 is trying to acquire lock: ffff8880aa768528 (&fi->i_sem){++++}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2179 [inline] ffff8880aa768528 (&fi->i_sem){++++}-{3:3}, at: f2fs_add_inline_entry+0x3a4/0x760 fs/f2fs/inline.c:645 but task is already holding lock: ffff8880aa7690a8 (&fi->i_xattr_sem){.+.+}-{3:3}, at: f2fs_down_read fs/f2fs/f2fs.h:2154 [inline] ffff8880aa7690a8 (&fi->i_xattr_sem){.+.+}-{3:3}, at: f2fs_add_dentry+0x9b/0x1e0 fs/f2fs/dir.c:814 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&fi->i_xattr_sem){.+.+}-{3:3}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 down_read+0x43/0x2e0 kernel/locking/rwsem.c:1520 f2fs_down_read fs/f2fs/f2fs.h:2154 [inline] f2fs_getxattr+0xb4/0x1460 fs/f2fs/xattr.c:531 __f2fs_get_acl+0x52/0x8a0 fs/f2fs/acl.c:179 f2fs_acl_create fs/f2fs/acl.c:375 [inline] f2fs_init_acl+0xd3/0x960 fs/f2fs/acl.c:418 f2fs_init_inode_metadata+0xaa0/0x11d0 fs/f2fs/dir.c:587 f2fs_add_regular_entry+0x866/0xe00 fs/f2fs/dir.c:771 f2fs_add_dentry+0xf3/0x1e0 fs/f2fs/dir.c:819 f2fs_do_add_link+0x21a/0x340 fs/f2fs/dir.c:858 f2fs_add_link fs/f2fs/f2fs.h:3530 [inline] f2fs_create+0x749/0xa10 fs/f2fs/namei.c:367 lookup_open fs/namei.c:3413 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x12f1/0x2e60 fs/namei.c:3711 do_filp_open+0x230/0x480 fs/namei.c:3741 do_sys_openat2+0x13b/0x500 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_open fs/open.c:1342 [inline] __se_sys_open fs/open.c:1338 [inline] __x64_sys_open+0x221/0x270 fs/open.c:1338 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&fi->i_sem){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3824 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5048 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 down_write+0x36/0x60 kernel/locking/rwsem.c:1573 f2fs_down_write fs/f2fs/f2fs.h:2179 [inline] f2fs_add_inline_entry+0x3a4/0x760 fs/f2fs/inline.c:645 f2fs_add_dentry+0xb6/0x1e0 fs/f2fs/dir.c:815 f2fs_do_add_link+0x21a/0x340 fs/f2fs/dir.c:858 f2fs_add_link fs/f2fs/f2fs.h:3530 [inline] f2fs_mkdir+0x2f1/0x520 fs/f2fs/namei.c:771 vfs_mkdir+0x3b6/0x590 fs/namei.c:4036 do_mkdirat+0x260/0x520 fs/namei.c:4061 __do_sys_mkdirat fs/namei.c:4076 [inline] __se_sys_mkdirat fs/namei.c:4074 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4074 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&fi->i_xattr_sem); lock(&fi->i_sem); lock(&fi->i_xattr_sem); lock(&fi->i_sem); *** DEADLOCK *** 4 locks held by syz-executor.2/15150: #0: ffff88807a1ec460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393 #1: ffff8880aa768a38 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:791 [inline] #1: ffff8880aa768a38 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: filename_create+0x256/0x530 fs/namei.c:3807 #2: ffff88802a70c3b0 (&sbi->cp_rwsem){++++}-{3:3}, at: f2fs_down_read fs/f2fs/f2fs.h:2154 [inline] #2: ffff88802a70c3b0 (&sbi->cp_rwsem){++++}-{3:3}, at: f2fs_lock_op fs/f2fs/f2fs.h:2197 [inline] #2: ffff88802a70c3b0 (&sbi->cp_rwsem){++++}-{3:3}, at: f2fs_mkdir+0x221/0x520 fs/f2fs/namei.c:770 #3: ffff8880aa7690a8 (&fi->i_xattr_sem){.+.+}-{3:3}, at: f2fs_down_read fs/f2fs/f2fs.h:2154 [inline] #3: ffff8880aa7690a8 (&fi->i_xattr_sem){.+.+}-{3:3}, at: f2fs_add_dentry+0x9b/0x1e0 fs/f2fs/dir.c:814 stack backtrace: CPU: 0 PID: 15150 Comm: syz-executor.2 Not tainted 6.1.53-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3824 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5048 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 down_write+0x36/0x60 kernel/locking/rwsem.c:1573 f2fs_down_write fs/f2fs/f2fs.h:2179 [inline] f2fs_add_inline_entry+0x3a4/0x760 fs/f2fs/inline.c:645 f2fs_add_dentry+0xb6/0x1e0 fs/f2fs/dir.c:815 f2fs_do_add_link+0x21a/0x340 fs/f2fs/dir.c:858 f2fs_add_link fs/f2fs/f2fs.h:3530 [inline] f2fs_mkdir+0x2f1/0x520 fs/f2fs/namei.c:771 vfs_mkdir+0x3b6/0x590 fs/namei.c:4036 do_mkdirat+0x260/0x520 fs/namei.c:4061 __do_sys_mkdirat fs/namei.c:4076 [inline] __se_sys_mkdirat fs/namei.c:4074 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4074 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f1760e7cae9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f1761b3e0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007f1760f9bf80 RCX: 00007f1760e7cae9 RDX: 0000000000000000 RSI: 0000000020000440 RDI: 0000000000000004 RBP: 00007f1760ec847a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f1760f9bf80 R15: 00007ffd36069588