BTRFS info (device loop1): clearing compat-ro feature flag for FREE_SPACE_TREE (0x1) BTRFS info (device loop1): clearing compat-ro feature flag for FREE_SPACE_TREE_VALID (0x2) ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.1.469/6956 is trying to acquire lock: ffff88805e92cac0 (&type->i_mutex_dir_key#14){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:797 [inline] ffff88805e92cac0 (&type->i_mutex_dir_key#14){++++}-{3:3}, at: lookup_slow+0x46/0x70 fs/namei.c:1687 but task is already holding lock: ffff888024d16ce0 (&fs_devs->device_list_mutex){+.+.}-{3:3}, at: btrfs_free_stale_devices+0x186/0xa60 fs/btrfs/volumes.c:603 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&fs_devs->device_list_mutex){+.+.}-{3:3}: __mutex_lock_common+0x1eb/0x2390 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 insert_dev_extents fs/btrfs/block-group.c:2399 [inline] btrfs_create_pending_block_groups+0x4a6/0xe50 fs/btrfs/block-group.c:2449 __btrfs_end_transaction+0x154/0x650 fs/btrfs/transaction.c:1016 flush_space+0x43e/0xc50 fs/btrfs/space-info.c:674 btrfs_async_reclaim_data_space+0x113/0x440 fs/btrfs/space-info.c:1169 process_one_work+0x863/0x1000 kernel/workqueue.c:2310 worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457 kthread+0x436/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 -> #1 (sb_internal#4){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1811 [inline] sb_start_intwrite include/linux/fs.h:1928 [inline] start_transaction+0x5bc/0x1130 fs/btrfs/transaction.c:680 btrfs_dirty_inode+0xc5/0x1c0 fs/btrfs/inode.c:6451 inode_update_time fs/inode.c:1893 [inline] touch_atime+0x2f6/0x620 fs/inode.c:1966 file_accessed include/linux/fs.h:2522 [inline] iterate_dir+0x482/0x560 fs/readdir.c:70 __do_sys_getdents64 fs/readdir.c:369 [inline] __se_sys_getdents64+0xe5/0x260 fs/readdir.c:354 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #0 (&type->i_mutex_dir_key#14){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623 down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 inode_lock_shared include/linux/fs.h:797 [inline] lookup_slow+0x46/0x70 fs/namei.c:1687 walk_component+0x319/0x460 fs/namei.c:1984 lookup_last fs/namei.c:2439 [inline] path_lookupat+0x169/0x440 fs/namei.c:2463 filename_lookup+0x1e2/0x4f0 fs/namei.c:2492 kern_path+0x37/0x190 fs/namei.c:2590 lookup_bdev+0xbd/0x270 block/bdev.c:982 device_matched fs/btrfs/volumes.c:568 [inline] btrfs_free_stale_devices+0x6db/0xa60 fs/btrfs/volumes.c:608 btrfs_forget_devices+0x52/0x80 fs/btrfs/volumes.c:1431 btrfs_control_ioctl+0x104/0x220 fs/btrfs/super.c:2450 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 other info that might help us debug this: Chain exists of: &type->i_mutex_dir_key#14 --> sb_internal#4 --> &fs_devs->device_list_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&fs_devs->device_list_mutex); lock(sb_internal#4); lock(&fs_devs->device_list_mutex); lock(&type->i_mutex_dir_key#14); *** DEADLOCK *** 2 locks held by syz.1.469/6956: #0: ffffffff8c606668 (uuid_mutex){+.+.}-{3:3}, at: btrfs_forget_devices+0x1a/0x80 fs/btrfs/volumes.c:1430 #1: ffff888024d16ce0 (&fs_devs->device_list_mutex){+.+.}-{3:3}, at: btrfs_free_stale_devices+0x186/0xa60 fs/btrfs/volumes.c:603 stack backtrace: CPU: 1 PID: 6956 Comm: syz.1.469 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623 down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 inode_lock_shared include/linux/fs.h:797 [inline] lookup_slow+0x46/0x70 fs/namei.c:1687 walk_component+0x319/0x460 fs/namei.c:1984 lookup_last fs/namei.c:2439 [inline] path_lookupat+0x169/0x440 fs/namei.c:2463 filename_lookup+0x1e2/0x4f0 fs/namei.c:2492 kern_path+0x37/0x190 fs/namei.c:2590 lookup_bdev+0xbd/0x270 block/bdev.c:982 device_matched fs/btrfs/volumes.c:568 [inline] btrfs_free_stale_devices+0x6db/0xa60 fs/btrfs/volumes.c:608 btrfs_forget_devices+0x52/0x80 fs/btrfs/volumes.c:1431 btrfs_control_ioctl+0x104/0x220 fs/btrfs/super.c:2450 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7f04e1e74749 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f04e00db038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f04e20cafa0 RCX: 00007f04e1e74749 RDX: 0000200000000180 RSI: 0000000050009405 RDI: 000000000000000e RBP: 00007f04e1ef8f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f04e20cb038 R14: 00007f04e20cafa0 R15: 00007ffe98ef8ec8