FAT-fs (loop4): Directory bread(block 65) failed FAT-fs (loop3): Directory bread(block 68) failed FAT-fs (loop4): Directory bread(block 66) failed ====================================================== FAT-fs (loop3): Directory bread(block 69) failed WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.1/25637 is trying to acquire lock: 0000000007cf4ce9 (&fs_info->qgroup_ioctl_lock){+.+.}, at: btrfs_qgroup_inherit+0xde/0x1c60 fs/btrfs/qgroup.c:2284 but task is already holding lock: 000000008e628a8c (sb_internal#3){.+.+}, at: sb_start_intwrite include/linux/fs.h:1626 [inline] 000000008e628a8c (sb_internal#3){.+.+}, at: start_transaction+0xa37/0xf90 fs/btrfs/transaction.c:528 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: FAT-fs (loop4): Directory bread(block 67) failed -> #1 (sb_internal#3){.+.+}: sb_start_intwrite include/linux/fs.h:1626 [inline] start_transaction+0xa37/0xf90 fs/btrfs/transaction.c:528 btrfs_quota_enable+0x169/0x10b0 fs/btrfs/qgroup.c:905 btrfs_ioctl_quota_ctl fs/btrfs/ioctl.c:5233 [inline] btrfs_ioctl+0x622c/0x76d0 fs/btrfs/ioctl.c:6021 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705 __do_sys_ioctl fs/ioctl.c:712 [inline] __se_sys_ioctl fs/ioctl.c:710 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&fs_info->qgroup_ioctl_lock){+.+.}: __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 btrfs_qgroup_inherit+0xde/0x1c60 fs/btrfs/qgroup.c:2284 create_subvol+0x3aa/0x1850 fs/btrfs/ioctl.c:617 btrfs_mksubvol+0xe1d/0x1160 fs/btrfs/ioctl.c:1007 btrfs_ioctl_snap_create_transid+0x2a7/0x430 fs/btrfs/ioctl.c:1771 btrfs_ioctl_snap_create+0x114/0x170 fs/btrfs/ioctl.c:1819 btrfs_ioctl+0x274b/0x76d0 fs/btrfs/ioctl.c:5932 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705 __do_sys_ioctl fs/ioctl.c:712 [inline] __se_sys_ioctl fs/ioctl.c:710 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_internal#3); lock(&fs_info->qgroup_ioctl_lock); lock(sb_internal#3); lock(&fs_info->qgroup_ioctl_lock); *** DEADLOCK *** 4 locks held by syz-executor.1/25637: #0: 00000000e067aa97 (sb_writers#15){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] #0: 00000000e067aa97 (sb_writers#15){.+.+}, at: mnt_want_write_file+0x63/0x1d0 fs/namespace.c:418 #1: 00000000f0a428aa (&type->i_mutex_dir_key#8/1){+.+.}, at: btrfs_mksubvol+0x156/0x1160 fs/btrfs/ioctl.c:975 #2: 000000004cafe815 (&fs_info->subvol_sem){++++}, at: btrfs_mksubvol+0x35b/0x1160 fs/btrfs/ioctl.c:998 #3: 000000008e628a8c (sb_internal#3){.+.+}, at: sb_start_intwrite include/linux/fs.h:1626 [inline] #3: 000000008e628a8c (sb_internal#3){.+.+}, at: start_transaction+0xa37/0xf90 fs/btrfs/transaction.c:528 stack backtrace: CPU: 1 PID: 25637 Comm: syz-executor.1 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1222 check_prev_add kernel/locking/lockdep.c:1866 [inline] check_prevs_add kernel/locking/lockdep.c:1979 [inline] validate_chain kernel/locking/lockdep.c:2420 [inline] __lock_acquire+0x30c9/0x3ff0 kernel/locking/lockdep.c:3416 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908 __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 FAT-fs (loop3): Directory bread(block 70) failed btrfs_qgroup_inherit+0xde/0x1c60 fs/btrfs/qgroup.c:2284 FAT-fs (loop4): Directory bread(block 68) failed create_subvol+0x3aa/0x1850 fs/btrfs/ioctl.c:617 FAT-fs (loop3): Directory bread(block 71) failed btrfs_mksubvol+0xe1d/0x1160 fs/btrfs/ioctl.c:1007 FAT-fs (loop4): Directory bread(block 69) failed FAT-fs (loop3): Directory bread(block 72) failed btrfs_ioctl_snap_create_transid+0x2a7/0x430 fs/btrfs/ioctl.c:1771 btrfs_ioctl_snap_create+0x114/0x170 fs/btrfs/ioctl.c:1819 FAT-fs (loop4): Directory bread(block 70) failed btrfs_ioctl+0x274b/0x76d0 fs/btrfs/ioctl.c:5932 FAT-fs (loop4): Directory bread(block 71) failed FAT-fs (loop3): Directory bread(block 73) failed FAT-fs (loop4): Directory bread(block 72) failed vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705 __do_sys_ioctl fs/ioctl.c:712 [inline] __se_sys_ioctl fs/ioctl.c:710 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7f4e85c050c9 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:00007f4e84177168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f4e85d24f80 RCX: 00007f4e85c050c9 RDX: 00000000200000c0 RSI: 000000005000940e RDI: 0000000000000005 RBP: 00007f4e85c60ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe9bd5346f R14: 00007f4e84177300 R15: 0000000000022000 FAT-fs (loop4): Directory bread(block 73) failed nla_parse: 29 callbacks suppressed netlink: 28 bytes leftover after parsing attributes in process `syz-executor.5'. FAT-fs (loop3): Directory bread(block 64) failed FAT-fs (loop3): Directory bread(block 65) failed netlink: 28 bytes leftover after parsing attributes in process `syz-executor.5'. FAT-fs (loop3): Directory bread(block 66) failed FAT-fs (loop3): Directory bread(block 67) failed FAT-fs (loop4): Directory bread(block 64) failed FAT-fs (loop4): Directory bread(block 65) failed FAT-fs (loop4): Directory bread(block 66) failed FAT-fs (loop3): Directory bread(block 68) failed FAT-fs (loop4): Directory bread(block 67) failed netlink: 28 bytes leftover after parsing attributes in process `syz-executor.5'. FAT-fs (loop3): Directory bread(block 69) failed FAT-fs (loop4): Directory bread(block 68) failed FAT-fs (loop3): Directory bread(block 70) failed FAT-fs (loop4): Directory bread(block 69) failed FAT-fs (loop3): Directory bread(block 71) failed FAT-fs (loop4): Directory bread(block 70) failed FAT-fs (loop3): Directory bread(block 72) failed FAT-fs (loop4): Directory bread(block 71) failed FAT-fs (loop3): Directory bread(block 73) failed FAT-fs (loop4): Directory bread(block 72) failed netlink: 28 bytes leftover after parsing attributes in process `syz-executor.5'. FAT-fs (loop4): Directory bread(block 73) failed netlink: 28 bytes leftover after parsing attributes in process `syz-executor.5'. FAT-fs (loop3): Directory bread(block 64) failed FAT-fs (loop3): Directory bread(block 65) failed FAT-fs (loop3): Directory bread(block 66) failed FAT-fs (loop3): Directory bread(block 67) failed netlink: 28 bytes leftover after parsing attributes in process `syz-executor.5'. FAT-fs (loop3): Directory bread(block 68) failed FAT-fs (loop4): Directory bread(block 64) failed FAT-fs (loop3): Directory bread(block 69) failed FAT-fs (loop4): Directory bread(block 65) failed FAT-fs (loop3): Directory bread(block 70) failed FAT-fs (loop4): Directory bread(block 66) failed netlink: 28 bytes leftover after parsing attributes in process `syz-executor.5'. FAT-fs (loop3): Directory bread(block 71) failed FAT-fs (loop4): Directory bread(block 67) failed FAT-fs (loop4): Directory bread(block 68) failed FAT-fs (loop3): Directory bread(block 72) failed FAT-fs (loop4): Directory bread(block 69) failed FAT-fs (loop3): Directory bread(block 73) failed FAT-fs (loop4): Directory bread(block 70) failed FAT-fs (loop4): Directory bread(block 71) failed FAT-fs (loop4): Directory bread(block 72) failed FAT-fs (loop4): Directory bread(block 73) failed BTRFS info (device loop1): unrecognized mount option 'ÿÿÿÿ_subB™Æ