F2FS-fs (loop0): invalid crc value F2FS-fs (loop0): Found nat_bits in checkpoint F2FS-fs (loop0): Try to recover 1th superblock, ret: 0 F2FS-fs (loop0): Mounted with checkpoint version = 753bd00b ====================================================== WARNING: possible circular locking dependency detected 6.2.0-syzkaller-05251-g5b7c4cabbb65 #0 Not tainted ------------------------------------------------------ syz-executor.0/5386 is trying to acquire lock: ffff88802c1a4998 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0x93/0x120 mm/memory.c:5649 but task is already holding lock: ffff8880850f8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2213 [inline] ffff8880850f8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_ioc_get_encryption_pwsalt fs/f2fs/file.c:2350 [inline] ffff8880850f8088 (&sbi->sb_lock){++++}-{3:3}, at: __f2fs_ioctl+0x362b/0xb4d0 fs/f2fs/file.c:4169 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #4 (&sbi->sb_lock){++++}-{3:3}: lock_acquire+0x23e/0x630 kernel/locking/lockdep.c:5669 down_write+0x3a/0x50 kernel/locking/rwsem.c:1573 f2fs_down_write fs/f2fs/f2fs.h:2213 [inline] f2fs_handle_error+0xef/0x240 fs/f2fs/super.c:3920 f2fs_new_node_page+0x815/0xb60 fs/f2fs/node.c:1303 f2fs_get_dnode_of_data+0x73f/0x1e40 fs/f2fs/node.c:810 f2fs_reserve_block+0x54/0x250 fs/f2fs/data.c:1199 f2fs_get_new_data_page+0x186/0x770 fs/f2fs/data.c:1387 f2fs_add_regular_entry+0x64b/0xe10 fs/f2fs/dir.c:754 f2fs_add_dentry fs/f2fs/dir.c:816 [inline] f2fs_do_add_link+0x2c6/0x4e0 fs/f2fs/dir.c:855 f2fs_add_link fs/f2fs/f2fs.h:3564 [inline] f2fs_mkdir+0x2f5/0x530 fs/f2fs/namei.c:767 vfs_mkdir+0x29d/0x450 fs/namei.c:4038 do_mkdirat+0x264/0x520 fs/namei.c:4061 __do_sys_mkdirat fs/namei.c:4076 [inline] __se_sys_mkdirat fs/namei.c:4074 [inline] __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4074 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 -> #3 (&sbi->cp_rwsem){++++}-{3:3}: lock_acquire+0x23e/0x630 kernel/locking/lockdep.c:5669 down_read+0x3d/0x50 kernel/locking/rwsem.c:1520 f2fs_down_read fs/f2fs/f2fs.h:2188 [inline] f2fs_lock_op fs/f2fs/f2fs.h:2231 [inline] f2fs_do_truncate_blocks+0x25e/0xf10 fs/f2fs/file.c:688 f2fs_truncate_blocks+0x10d/0x2f0 fs/f2fs/file.c:751 f2fs_truncate+0x497/0x8d0 fs/f2fs/file.c:803 f2fs_setattr+0xbf1/0x1270 fs/f2fs/file.c:1010 notify_change+0xc8b/0xf40 fs/attr.c:482 do_truncate+0x220/0x300 fs/open.c:66 handle_truncate fs/namei.c:3219 [inline] do_open fs/namei.c:3564 [inline] path_openat+0x294e/0x3170 fs/namei.c:3715 do_filp_open+0x234/0x490 fs/namei.c:3742 do_sys_openat2+0x13f/0x500 fs/open.c:1312 do_sys_open fs/open.c:1328 [inline] __do_sys_openat fs/open.c:1344 [inline] __se_sys_openat fs/open.c:1339 [inline] __x64_sys_openat+0x247/0x290 fs/open.c:1339 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 -> #2 (mapping.invalidate_lock#5){++++}-{3:3}: lock_acquire+0x23e/0x630 kernel/locking/lockdep.c:5669 down_read+0x3d/0x50 kernel/locking/rwsem.c:1520 filemap_invalidate_lock_shared include/linux/fs.h:811 [inline] f2fs_vm_page_mkwrite+0x547/0x1440 fs/f2fs/file.c:104 do_page_mkwrite+0x1a1/0x600 mm/memory.c:2943 wp_page_shared mm/memory.c:3291 [inline] do_wp_page+0x506/0x3280 mm/memory.c:3373 handle_pte_fault mm/memory.c:4952 [inline] __handle_mm_fault mm/memory.c:5076 [inline] handle_mm_fault+0x2395/0x51e0 mm/memory.c:5222 do_user_addr_fault arch/x86/mm/fault.c:1428 [inline] handle_page_fault arch/x86/mm/fault.c:1519 [inline] exc_page_fault+0x685/0x8a0 arch/x86/mm/fault.c:1575 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570 -> #1 (sb_pagefaults#2){.+.+}-{0:0}: lock_acquire+0x23e/0x630 kernel/locking/lockdep.c:5669 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write+0x58/0x1c0 include/linux/fs.h:1475 sb_start_pagefault include/linux/fs.h:1579 [inline] f2fs_vm_page_mkwrite+0x47b/0x1440 fs/f2fs/file.c:99 do_page_mkwrite+0x1a1/0x600 mm/memory.c:2943 wp_page_shared mm/memory.c:3291 [inline] do_wp_page+0x506/0x3280 mm/memory.c:3373 handle_pte_fault mm/memory.c:4952 [inline] __handle_mm_fault mm/memory.c:5076 [inline] handle_mm_fault+0x2395/0x51e0 mm/memory.c:5222 do_user_addr_fault arch/x86/mm/fault.c:1428 [inline] handle_page_fault arch/x86/mm/fault.c:1519 [inline] exc_page_fault+0x685/0x8a0 arch/x86/mm/fault.c:1575 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570 -> #0 (&mm->mmap_lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain+0x166b/0x58e0 kernel/locking/lockdep.c:3832 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056 lock_acquire+0x23e/0x630 kernel/locking/lockdep.c:5669 __might_fault+0xba/0x120 mm/memory.c:5650 _copy_to_user+0x2a/0x130 lib/usercopy.c:36 copy_to_user include/linux/uaccess.h:169 [inline] f2fs_ioc_get_encryption_pwsalt fs/f2fs/file.c:2365 [inline] __f2fs_ioctl+0xaee1/0xb4d0 fs/f2fs/file.c:4169 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856 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 other info that might help us debug this: Chain exists of: &mm->mmap_lock --> &sbi->cp_rwsem --> &sbi->sb_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->sb_lock); lock(&sbi->cp_rwsem); lock(&sbi->sb_lock); lock(&mm->mmap_lock); *** DEADLOCK *** 2 locks held by syz-executor.0/5386: #0: ffff888077138460 (sb_writers#21){.+.+}-{0:0}, at: mnt_want_write_file+0x5e/0x1f0 fs/namespace.c:438 #1: ffff8880850f8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2213 [inline] #1: ffff8880850f8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_ioc_get_encryption_pwsalt fs/f2fs/file.c:2350 [inline] #1: ffff8880850f8088 (&sbi->sb_lock){++++}-{3:3}, at: __f2fs_ioctl+0x362b/0xb4d0 fs/f2fs/file.c:4169 stack backtrace: CPU: 1 PID: 5386 Comm: syz-executor.0 Not tainted 6.2.0-syzkaller-05251-g5b7c4cabbb65 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 check_noncircular+0x2fe/0x3b0 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+0x166b/0x58e0 kernel/locking/lockdep.c:3832 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056 lock_acquire+0x23e/0x630 kernel/locking/lockdep.c:5669 __might_fault+0xba/0x120 mm/memory.c:5650 _copy_to_user+0x2a/0x130 lib/usercopy.c:36 copy_to_user include/linux/uaccess.h:169 [inline] f2fs_ioc_get_encryption_pwsalt fs/f2fs/file.c:2365 [inline] __f2fs_ioctl+0xaee1/0xb4d0 fs/f2fs/file.c:4169 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856 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:0x7fe9fae8c0f9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fe9fbc55168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fe9fafabf80 RCX: 00007fe9fae8c0f9 RDX: 00000000200087c0 RSI: 0000000040106614 RDI: 0000000000000005 RBP: 00007fe9faee7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc00f0a9bf R14: 00007fe9fbc55300 R15: 0000000000022000