syzbot |
sign-in | mailing list | source | docs |
BTRFS: device fsid 24c7a497-3402-47dd-bef8-82358f5f30e0 devid 1 transid 8 /dev/loop0 BTRFS info (device loop0): using free space tree BTRFS info (device loop0): has skinny extents ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor313/8100 is trying to acquire lock: 000000000d7bde88 (&fs_info->qgroup_ioctl_lock){+.+.}, at: btrfs_del_qgroup_relation+0x45/0x70 fs/btrfs/qgroup.c:1366 but task is already holding lock: 000000001146e189 (sb_internal#2){.+.+}, at: sb_start_intwrite include/linux/fs.h:1626 [inline] 000000001146e189 (sb_internal#2){.+.+}, 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#2){.+.+}: 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_del_qgroup_relation+0x45/0x70 fs/btrfs/qgroup.c:1366 btrfs_ioctl_qgroup_assign fs/btrfs/ioctl.c:5282 [inline] btrfs_ioctl+0x6004/0x76d0 fs/btrfs/ioctl.c:6023 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#2); lock(&fs_info->qgroup_ioctl_lock); lock(sb_internal#2); lock(&fs_info->qgroup_ioctl_lock); *** DEADLOCK *** 2 locks held by syz-executor313/8100: #0: 000000009d93883e (sb_writers#11){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] #0: 000000009d93883e (sb_writers#11){.+.+}, at: mnt_want_write_file+0x63/0x1d0 fs/namespace.c:418 #1: 000000001146e189 (sb_internal#2){.+.+}, at: sb_start_intwrite include/linux/fs.h:1626 [inline] #1: 000000001146e189 (sb_internal#2){.+.+}, at: start_transaction+0xa37/0xf90 fs/btrfs/transaction.c:528 stack backtrace: CPU: 0 PID: 8100 Comm: syz-executor313 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 btrfs_del_qgroup_relation+0x45/0x70 fs/btrfs/qgroup.c:1366 btrfs_ioctl_qgroup_assign fs/btrfs/ioctl.c:5282 [inline] btrfs_ioctl+0x6004/0x76d0 fs/btrfs/ioctl.c:6023 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:0x7f26b4e08af9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 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 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe1000e338 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007f26b4e08af9 RDX: 0000000020000e80 RSI: 0000000040189429 RDI: 0000000000000005
Time | Kernel | Commit | Syzkaller | Config | Log | Report | Syz repro | C repro | VM info | Assets (help?) | Manager | Title |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2022/12/03 02:05 | linux-4.19.y | 3f8a27f9e27b | e080de16 | .config | console log | report | syz | C | [disk image] [vmlinux] [mounted in repro] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | |
2023/02/05 13:03 | linux-4.19.y | 3f8a27f9e27b | be607b78 | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2023/01/29 23:37 | linux-4.19.y | 3f8a27f9e27b | 9dfcf09c | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2023/01/16 02:28 | linux-4.19.y | 3f8a27f9e27b | a63719e7 | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2023/01/11 22:48 | linux-4.19.y | 3f8a27f9e27b | 96166539 | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2023/01/03 03:11 | linux-4.19.y | 3f8a27f9e27b | ab32d508 | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2022/12/27 17:41 | linux-4.19.y | 3f8a27f9e27b | 44712fbc | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2022/12/26 20:42 | linux-4.19.y | 3f8a27f9e27b | 9da18ae8 | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2022/12/26 20:40 | linux-4.19.y | 3f8a27f9e27b | 9da18ae8 | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2022/12/26 20:29 | linux-4.19.y | 3f8a27f9e27b | 9da18ae8 | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2022/12/24 14:42 | linux-4.19.y | 3f8a27f9e27b | 9da18ae8 | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2022/12/14 16:38 | linux-4.19.y | 3f8a27f9e27b | b18f0a64 | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2022/12/08 11:46 | linux-4.19.y | 3f8a27f9e27b | d88f3abb | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation | ||
2022/12/03 01:52 | linux-4.19.y | 3f8a27f9e27b | e080de16 | .config | console log | report | info | [disk image] [vmlinux] | ci2-linux-4-19 | possible deadlock in btrfs_del_qgroup_relation |