syzbot

 sign-in | mailing list | source | docs
🐞 Open [776]
🐞 Fixed [129]
🐞 Invalid [850]
⬇ Missing Backports [72]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

possible deadlock in lookup_slow (2)

Status: upstream: reported on 2025/05/16 17:47
Reported-by: syzbot+8dab26395833f6231fa9@syzkaller.appspotmail.com
First crash: 108d, last: 21d
▶ ▼ Similar bugs (8)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in lookup_slow (3) kernfs 4 355 9d14h 775d 0/29 upstream: reported on 2023/07/19 13:17
linux-5.15 possible deadlock in lookup_slow 4 11 730d 902d 0/3 auto-obsoleted due to no activity on 2023/12/11 13:10
linux-4.19 possible deadlock in lookup_slow 4 22 1905d 2331d 0/1 auto-closed as invalid on 2020/10/12 22:59
linux-6.1 possible deadlock in lookup_slow 4 1 213d 213d 0/3 auto-obsoleted due to no activity on 2025/05/11 18:32
upstream possible deadlock in lookup_slow fs 4 139 2291d 2532d 0/29 auto-closed as invalid on 2019/10/25 08:42
linux-5.15 possible deadlock in lookup_slow (2) origin:lts-only 4 C 124 14d 628d 0/3 upstream: reported C repro on 2023/12/13 22:35
linux-4.14 possible deadlock in lookup_slow 4 C 2027 910d 2200d 0/1 upstream: reported C repro on 2019/08/24 01:53
upstream possible deadlock in lookup_slow (2) fs 4 7 2059d 2104d 0/29 auto-closed as invalid on 2020/05/11 09:17

Sample crash report:
loop2: detected capacity change from 0 to 32768
======================================================
WARNING: possible circular locking dependency detected
6.1.147-syzkaller #0 Not tainted
------------------------------------------------------
syz.2.483/6917 is trying to acquire lock:
ffff0000c09208e0 (&type->i_mutex_dir_key#2){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
ffff0000c09208e0 (&type->i_mutex_dir_key#2){++++}-{3:3}, at: lookup_slow+0x4c/0x80 fs/namei.c:1706

but task is already holding lock:
ffff0000f5ce34e0 (&fs_devs->device_list_mutex){+.+.}-{3:3}, at: device_list_add+0x7cc/0x1be0 fs/btrfs/volumes.c:860

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (&fs_devs->device_list_mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x190/0x1f38 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
       insert_dev_extents fs/btrfs/block-group.c:2497 [inline]
       btrfs_create_pending_block_groups+0x464/0xd64 fs/btrfs/block-group.c:2548
       __btrfs_end_transaction+0x134/0x5fc fs/btrfs/transaction.c:1012
       btrfs_end_transaction+0x24/0x34 fs/btrfs/transaction.c:1051
       flush_space+0x864/0xcdc fs/btrfs/space-info.c:770
       btrfs_async_reclaim_data_space+0xf4/0x48c fs/btrfs/space-info.c:1296
       process_one_work+0x7f4/0x13a8 kernel/workqueue.c:2292
       worker_thread+0x8c8/0xfbc kernel/workqueue.c:2439
       kthread+0x250/0x2d8 kernel/kthread.c:376
       ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:849

-> #3 (btrfs_trans_num_extwriters){++++}-{0:0}:
       join_transaction+0x180/0xb6c fs/btrfs/transaction.c:303
       start_transaction+0x854/0x104c fs/btrfs/transaction.c:667
       btrfs_start_transaction+0x34/0x44 fs/btrfs/transaction.c:766
       btrfs_rebuild_free_space_tree+0xb0/0x6d4 fs/btrfs/free-space-tree.c:1319
       btrfs_start_pre_rw_mount+0x2c8/0x658 fs/btrfs/disk-io.c:3237
       open_ctree+0x1ae8/0x224c fs/btrfs/disk-io.c:3834
       btrfs_fill_super+0x1b4/0x2d4 fs/btrfs/super.c:1469
       btrfs_mount_root+0x730/0x780 fs/btrfs/super.c:1834
       legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
       vfs_get_tree+0x90/0x274 fs/super.c:1573
       fc_mount fs/namespace.c:1039 [inline]
       vfs_kern_mount+0xdc/0x178 fs/namespace.c:1069
       btrfs_mount+0x2a0/0x8dc fs/btrfs/super.c:1894
       legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
       vfs_get_tree+0x90/0x274 fs/super.c:1573
       do_new_mount+0x228/0x810 fs/namespace.c:3063
       path_mount+0x5b4/0xe78 fs/namespace.c:3393
       do_mount fs/namespace.c:3406 [inline]
       __do_sys_mount fs/namespace.c:3614 [inline]
       __se_sys_mount fs/namespace.c:3591 [inline]
       __arm64_sys_mount+0x49c/0x584 fs/namespace.c:3591
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

-> #2 (btrfs_trans_num_writers){++++}-{0:0}:
       __lock_release kernel/locking/lockdep.c:5376 [inline]
       lock_release+0x308/0x910 kernel/locking/lockdep.c:5682
       percpu_up_read include/linux/percpu-rwsem.h:99 [inline]
       __sb_end_write include/linux/fs.h:1886 [inline]
       sb_end_intwrite+0x54/0x360 include/linux/fs.h:1942
       __btrfs_end_transaction+0x1f4/0x5fc fs/btrfs/transaction.c:1017
       btrfs_end_transaction+0x24/0x34 fs/btrfs/transaction.c:1051
       btrfs_dirty_inode+0x16c/0x1c0 fs/btrfs/inode.c:6291
       btrfs_update_time+0x170/0x18c fs/btrfs/inode.c:6319
       inode_update_time fs/inode.c:1958 [inline]
       touch_atime+0x364/0x7d0 fs/inode.c:2031
       file_accessed include/linux/fs.h:2600 [inline]
       btrfs_file_mmap+0xb0/0x11c fs/btrfs/file.c:2053
       call_mmap include/linux/fs.h:2270 [inline]
       mmap_file+0x6c/0xc8 mm/util.c:1109
       __mmap_region mm/mmap.c:2768 [inline]
       mmap_region+0xcc8/0x1860 mm/mmap.c:2912
       do_mmap+0x978/0x10dc mm/mmap.c:1432
       vm_mmap_pgoff+0x184/0x284 mm/util.c:520
       ksys_mmap_pgoff+0x3b8/0x5a0 mm/mmap.c:1478
       __do_sys_mmap arch/arm64/kernel/sys.c:28 [inline]
       __se_sys_mmap arch/arm64/kernel/sys.c:21 [inline]
       __arm64_sys_mmap+0xf8/0x110 arch/arm64/kernel/sys.c:21
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       __might_fault+0xc4/0x124 mm/memory.c:5852
       filldir64+0x2cc/0x8fc fs/readdir.c:335
       dir_emit_dot include/linux/fs.h:3701 [inline]
       dir_emit_dots include/linux/fs.h:3712 [inline]
       dcache_readdir+0x140/0x62c fs/libfs.c:197
       iterate_dir+0x1f0/0x4cc fs/readdir.c:-1
       __do_sys_getdents64 fs/readdir.c:369 [inline]
       __se_sys_getdents64 fs/readdir.c:354 [inline]
       __arm64_sys_getdents64+0x11c/0x318 fs/readdir.c:354
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

-> #0 (&type->i_mutex_dir_key#2){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain kernel/locking/lockdep.c:3825 [inline]
       __lock_acquire+0x293c/0x6544 kernel/locking/lockdep.c:5049
       lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662
       down_read+0x64/0x304 kernel/locking/rwsem.c:1520
       inode_lock_shared include/linux/fs.h:768 [inline]
       lookup_slow+0x4c/0x80 fs/namei.c:1706
       walk_component+0x270/0x364 fs/namei.c:1998
       lookup_last fs/namei.c:2455 [inline]
       path_lookupat+0x13c/0x3d0 fs/namei.c:2479
       filename_lookup+0x190/0x42c fs/namei.c:2508
       kern_path+0x48/0x6c fs/namei.c:2606
       is_same_device fs/btrfs/volumes.c:695 [inline]
       device_list_add+0x1208/0x1be0 fs/btrfs/volumes.c:928
       btrfs_scan_one_device+0x364/0x570 fs/btrfs/volumes.c:1461
       btrfs_mount_root+0x404/0x780 fs/btrfs/super.c:1796
       legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
       vfs_get_tree+0x90/0x274 fs/super.c:1573
       fc_mount fs/namespace.c:1039 [inline]
       vfs_kern_mount+0xdc/0x178 fs/namespace.c:1069
       btrfs_mount+0x2a0/0x8dc fs/btrfs/super.c:1894
       legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
       vfs_get_tree+0x90/0x274 fs/super.c:1573
       do_new_mount+0x228/0x810 fs/namespace.c:3063
       path_mount+0x5b4/0xe78 fs/namespace.c:3393
       do_mount fs/namespace.c:3406 [inline]
       __do_sys_mount fs/namespace.c:3614 [inline]
       __se_sys_mount fs/namespace.c:3591 [inline]
       __arm64_sys_mount+0x49c/0x584 fs/namespace.c:3591
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

other info that might help us debug this:

Chain exists of:
  &type->i_mutex_dir_key#2 --> btrfs_trans_num_extwriters --> &fs_devs->device_list_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&fs_devs->device_list_mutex);
                               lock(btrfs_trans_num_extwriters);
                               lock(&fs_devs->device_list_mutex);
  lock(&type->i_mutex_dir_key#2);

 *** DEADLOCK ***

2 locks held by syz.2.483/6917:
 #0: ffff8000157c3d68 (uuid_mutex){+.+.}-{3:3}, at: btrfs_mount_root+0x1f4/0x780 fs/btrfs/super.c:1789
 #1: ffff0000f5ce34e0 (&fs_devs->device_list_mutex){+.+.}-{3:3}, at: device_list_add+0x7cc/0x1be0 fs/btrfs/volumes.c:860

stack backtrace:
CPU: 0 PID: 6917 Comm: syz.2.483 Not tainted 6.1.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/18/2025
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2048
 check_noncircular+0x240/0x2d4 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3090 [inline]
 check_prevs_add kernel/locking/lockdep.c:3209 [inline]
 validate_chain kernel/locking/lockdep.c:3825 [inline]
 __lock_acquire+0x293c/0x6544 kernel/locking/lockdep.c:5049
 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662
 down_read+0x64/0x304 kernel/locking/rwsem.c:1520
 inode_lock_shared include/linux/fs.h:768 [inline]
 lookup_slow+0x4c/0x80 fs/namei.c:1706
 walk_component+0x270/0x364 fs/namei.c:1998
 lookup_last fs/namei.c:2455 [inline]
 path_lookupat+0x13c/0x3d0 fs/namei.c:2479
 filename_lookup+0x190/0x42c fs/namei.c:2508
 kern_path+0x48/0x6c fs/namei.c:2606
 is_same_device fs/btrfs/volumes.c:695 [inline]
 device_list_add+0x1208/0x1be0 fs/btrfs/volumes.c:928
 btrfs_scan_one_device+0x364/0x570 fs/btrfs/volumes.c:1461
 btrfs_mount_root+0x404/0x780 fs/btrfs/super.c:1796
 legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
 vfs_get_tree+0x90/0x274 fs/super.c:1573
 fc_mount fs/namespace.c:1039 [inline]
 vfs_kern_mount+0xdc/0x178 fs/namespace.c:1069
 btrfs_mount+0x2a0/0x8dc fs/btrfs/super.c:1894
 legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
 vfs_get_tree+0x90/0x274 fs/super.c:1573
 do_new_mount+0x228/0x810 fs/namespace.c:3063
 path_mount+0x5b4/0xe78 fs/namespace.c:3393
 do_mount fs/namespace.c:3406 [inline]
 __do_sys_mount fs/namespace.c:3614 [inline]
 __se_sys_mount fs/namespace.c:3591 [inline]
 __arm64_sys_mount+0x49c/0x584 fs/namespace.c:3591
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
BTRFS info (device loop2): first mount of filesystem 395ef67a-297e-477c-816d-cd80a5b93e5d
BTRFS info (device loop2): using sha256 (sha256-ce) checksum algorithm
BTRFS info (device loop2): using free space tree
BTRFS info (device loop2): enabling ssd optimizations
__sock_release: fasync list not empty!

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/11 04:55 linux-6.1.y 3594f306da12 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in lookup_slow
2025/06/15 07:16 linux-6.1.y 58485ff1a74f 5f4b362d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in lookup_slow
2025/05/16 17:47 linux-6.1.y 02b72ccb5f9d cfde8269 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in lookup_slow
* Struck through repros no longer work on HEAD.