loop3: detected capacity change from 0 to 32768 BTRFS info (device loop3): using sha256 (sha256-ni) checksum algorithm BTRFS info (device loop3): using free space tree BTRFS info (device loop3): enabling ssd optimizations ====================================================== WARNING: possible circular locking dependency detected 6.1.0-rc7-syzkaller-00123-ga4412fdd49dc #0 Not tainted ------------------------------------------------------ syz-executor.3/17072 is trying to acquire lock: ffff88803bd4bc18 (btrfs-tree-01){++++}-{3:3}, at: __btrfs_tree_read_lock+0x32/0x350 fs/btrfs/locking.c:134 but task is already holding lock: ffff88803d9f20f8 (btrfs-tree-00){++++}-{3:3}, at: __btrfs_tree_read_lock+0x32/0x350 fs/btrfs/locking.c:134 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (btrfs-tree-00){++++}-{3:3}: down_read_nested+0x9e/0x450 kernel/locking/rwsem.c:1634 __btrfs_tree_read_lock+0x32/0x350 fs/btrfs/locking.c:134 btrfs_search_slot+0x13a3/0x2c70 fs/btrfs/ctree.c:2133 btrfs_init_root_free_objectid+0xc6/0x290 fs/btrfs/disk-io.c:5268 btrfs_init_fs_root fs/btrfs/disk-io.c:1467 [inline] btrfs_get_root_ref.part.0+0x706/0xba0 fs/btrfs/disk-io.c:1671 btrfs_get_root_ref fs/btrfs/disk-io.c:1645 [inline] btrfs_get_fs_root fs/btrfs/disk-io.c:1723 [inline] open_ctree+0x3b7c/0x4581 fs/btrfs/disk-io.c:3781 btrfs_fill_super fs/btrfs/super.c:1461 [inline] btrfs_mount_root.cold+0x15/0x162 fs/btrfs/super.c:1829 legacy_get_tree+0x109/0x220 fs/fs_context.c:610 vfs_get_tree+0x8d/0x2f0 fs/super.c:1531 fc_mount fs/namespace.c:1043 [inline] vfs_kern_mount.part.0+0xd3/0x170 fs/namespace.c:1073 vfs_kern_mount+0x40/0x60 fs/namespace.c:1060 btrfs_mount+0x238/0xa70 fs/btrfs/super.c:1889 legacy_get_tree+0x109/0x220 fs/fs_context.c:610 vfs_get_tree+0x8d/0x2f0 fs/super.c:1531 do_new_mount fs/namespace.c:3040 [inline] path_mount+0x132a/0x1e20 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __x64_sys_mount+0x283/0x300 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (btrfs-tree-01){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain kernel/locking/lockdep.c:3831 [inline] __lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5055 lock_acquire kernel/locking/lockdep.c:5668 [inline] lock_acquire+0x1e3/0x630 kernel/locking/lockdep.c:5633 down_read_nested+0x9e/0x450 kernel/locking/rwsem.c:1634 __btrfs_tree_read_lock+0x32/0x350 fs/btrfs/locking.c:134 btrfs_tree_read_lock fs/btrfs/locking.c:140 [inline] btrfs_read_lock_root_node+0x82/0x3a0 fs/btrfs/locking.c:279 btrfs_search_slot_get_root fs/btrfs/ctree.c:1665 [inline] btrfs_search_slot+0x3ca/0x2c70 fs/btrfs/ctree.c:1985 btrfs_lookup_inode+0xba/0x3e0 fs/btrfs/inode-item.c:407 btrfs_read_locked_inode+0xcd5/0x1520 fs/btrfs/inode.c:3958 btrfs_iget_path fs/btrfs/inode.c:5737 [inline] btrfs_iget+0x192/0x220 fs/btrfs/inode.c:5759 btrfs_search_path_in_tree_user fs/btrfs/ioctl.c:2851 [inline] btrfs_ioctl_ino_lookup_user+0x59f/0xbd0 fs/btrfs/ioctl.c:2995 btrfs_ioctl+0x5dd/0x5c40 fs/btrfs/ioctl.c:5561 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/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(btrfs-tree-00); lock(btrfs-tree-01); lock(btrfs-tree-00); lock(btrfs-tree-01); *** DEADLOCK *** 1 lock held by syz-executor.3/17072: #0: ffff88803d9f20f8 (btrfs-tree-00){++++}-{3:3}, at: __btrfs_tree_read_lock+0x32/0x350 fs/btrfs/locking.c:134 stack backtrace: CPU: 1 PID: 17072 Comm: syz-executor.3 Not tainted 6.1.0-rc7-syzkaller-00123-ga4412fdd49dc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2177 check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain kernel/locking/lockdep.c:3831 [inline] __lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5055 lock_acquire kernel/locking/lockdep.c:5668 [inline] lock_acquire+0x1e3/0x630 kernel/locking/lockdep.c:5633 down_read_nested+0x9e/0x450 kernel/locking/rwsem.c:1634 __btrfs_tree_read_lock+0x32/0x350 fs/btrfs/locking.c:134 btrfs_tree_read_lock fs/btrfs/locking.c:140 [inline] btrfs_read_lock_root_node+0x82/0x3a0 fs/btrfs/locking.c:279 btrfs_search_slot_get_root fs/btrfs/ctree.c:1665 [inline] btrfs_search_slot+0x3ca/0x2c70 fs/btrfs/ctree.c:1985 btrfs_lookup_inode+0xba/0x3e0 fs/btrfs/inode-item.c:407 btrfs_read_locked_inode+0xcd5/0x1520 fs/btrfs/inode.c:3958 btrfs_iget_path fs/btrfs/inode.c:5737 [inline] btrfs_iget+0x192/0x220 fs/btrfs/inode.c:5759 btrfs_search_path_in_tree_user fs/btrfs/ioctl.c:2851 [inline] btrfs_ioctl_ino_lookup_user+0x59f/0xbd0 fs/btrfs/ioctl.c:2995 btrfs_ioctl+0x5dd/0x5c40 fs/btrfs/ioctl.c:5561 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f5b3008c0d9 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:00007f5b30d08168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f5b301abf80 RCX: 00007f5b3008c0d9 RDX: 0000000020001200 RSI: 00000000d000943e RDI: 0000000000000004 RBP: 00007f5b300e7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe9d96d7cf R14: 00007f5b30d08300 R15: 0000000000022000