BTRFS info (device loop4): enabling ssd optimizations BTRFS info (device loop4): using spread ssd allocation scheme BTRFS info (device loop4): using free space tree BTRFS info (device loop4): has skinny extents ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.4/19946 is trying to acquire lock: 0000000071402cb8 (&fs_info->qgroup_ioctl_lock){+.+.}, at: btrfs_limit_qgroup+0x63/0x7b0 fs/btrfs/qgroup.c:1467 but task is already holding lock: 000000000e1dfc13 (sb_internal#3){.+.+}, at: sb_start_intwrite include/linux/fs.h:1626 [inline] 000000000e1dfc13 (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: -> #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_limit_qgroup+0x63/0x7b0 fs/btrfs/qgroup.c:1467 btrfs_ioctl_qgroup_limit fs/btrfs/ioctl.c:5386 [inline] btrfs_ioctl+0x3c0c/0x76d0 fs/btrfs/ioctl.c:6027 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 *** 2 locks held by syz-executor.4/19946: #0: 00000000c2246d0a (sb_writers#24){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] #0: 00000000c2246d0a (sb_writers#24){.+.+}, at: mnt_want_write_file+0x63/0x1d0 fs/namespace.c:418 #1: 000000000e1dfc13 (sb_internal#3){.+.+}, at: sb_start_intwrite include/linux/fs.h:1626 [inline] #1: 000000000e1dfc13 (sb_internal#3){.+.+}, at: start_transaction+0xa37/0xf90 fs/btrfs/transaction.c:528 stack backtrace: CPU: 1 PID: 19946 Comm: syz-executor.4 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 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 btrfs_limit_qgroup+0x63/0x7b0 fs/btrfs/qgroup.c:1467 btrfs_ioctl_qgroup_limit fs/btrfs/ioctl.c:5386 [inline] btrfs_ioctl+0x3c0c/0x76d0 fs/btrfs/ioctl.c:6027 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:0x7f46ad20e0c9 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:00007f46ab780168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f46ad32df80 RCX: 00007f46ad20e0c9 RDX: 0000000020000040 RSI: 000000008030942b RDI: 0000000000000004 RBP: 00007f46ad269ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc256f443f R14: 00007f46ab780300 R15: 0000000000022000 BTRFS error (device loop4): fail to start transaction for status update: -28 BTRFS info (device loop4): use zlib compression, level 3 BTRFS info (device loop4): enabling ssd optimizations BTRFS info (device loop4): using spread ssd allocation scheme BTRFS info (device loop4): using free space tree BTRFS info (device loop4): has skinny extents BTRFS error (device loop4): fail to start transaction for status update: -28 ieee80211 phy21: Selected rate control algorithm 'minstrel_ht' netlink: 'syz-executor.5': attribute type 1 has an invalid length. netlink: 240 bytes leftover after parsing attributes in process `syz-executor.5'. ieee80211 phy22: Selected rate control algorithm 'minstrel_ht' netlink: 'syz-executor.5': attribute type 1 has an invalid length. netlink: 240 bytes leftover after parsing attributes in process `syz-executor.5'. BTRFS info (device loop4): use zlib compression, level 3 BTRFS info (device loop4): enabling ssd optimizations ieee80211 phy23: Selected rate control algorithm 'minstrel_ht' BTRFS info (device loop4): using spread ssd allocation scheme BTRFS info (device loop4): using free space tree netlink: 'syz-executor.5': attribute type 1 has an invalid length. netlink: 240 bytes leftover after parsing attributes in process `syz-executor.5'. BTRFS info (device loop4): has skinny extents BTRFS error (device loop4): fail to start transaction for status update: -28 ieee80211 phy24: Selected rate control algorithm 'minstrel_ht' netlink: 'syz-executor.5': attribute type 1 has an invalid length. netlink: 240 bytes leftover after parsing attributes in process `syz-executor.5'. ieee80211 phy25: Selected rate control algorithm 'minstrel_ht' netlink: 'syz-executor.5': attribute type 1 has an invalid length. netlink: 240 bytes leftover after parsing attributes in process `syz-executor.5'. ieee80211 phy26: Selected rate control algorithm 'minstrel_ht' netlink: 'syz-executor.5': attribute type 1 has an invalid length. netlink: 240 bytes leftover after parsing attributes in process `syz-executor.5'. BTRFS info (device loop4): use zlib compression, level 3 BTRFS info (device loop4): enabling ssd optimizations BTRFS info (device loop4): using spread ssd allocation scheme BTRFS info (device loop4): using free space tree BTRFS info (device loop4): has skinny extents ieee80211 phy27: Selected rate control algorithm 'minstrel_ht' netlink: 'syz-executor.5': attribute type 1 has an invalid length. netlink: 240 bytes leftover after parsing attributes in process `syz-executor.5'. BTRFS error (device loop4): fail to start transaction for status update: -28 9pnet: Insufficient options for proto=fd 9pnet: Insufficient options for proto=fd batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_0 batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems! batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_0 batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems! batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_0 batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems! batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_0 batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems! batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_0 batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems! batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_0 batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems! 9pnet: Insufficient options for proto=fd 9pnet: Insufficient options for proto=fd 9pnet: Insufficient options for proto=fd 9pnet: Insufficient options for proto=fd 9pnet: Insufficient options for proto=fd 9pnet: Could not find request transport: xen