loop5: detected capacity change from 0 to 64 ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.5.4671/25398 is trying to acquire lock: ffff8880552120b0 (&tree->tree_lock#2/1){+.+.}-{3:3}, at: hfs_find_init+0x15b/0x1d0 fs/hfs/bfind.c:-1 but task is already holding lock: ffff8880625d4ef8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0xfb/0x13f0 fs/hfs/extent.c:397 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&HFS_I(tree->inode)->extents_lock){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x12d/0xaf0 kernel/locking/mutex.c:747 hfs_extend_file+0xfb/0x13f0 fs/hfs/extent.c:397 hfs_bmap_reserve+0x103/0x420 fs/hfs/btree.c:234 __hfs_ext_write_extent+0x1fa/0x470 fs/hfs/extent.c:121 __hfs_ext_cache_extent+0x6b/0x9b0 fs/hfs/extent.c:174 hfs_ext_read_extent fs/hfs/extent.c:202 [inline] hfs_extend_file+0x39c/0x13f0 fs/hfs/extent.c:401 hfs_get_block+0x40f/0xc50 fs/hfs/extent.c:353 __block_write_begin_int+0x55d/0x1a80 fs/buffer.c:1991 __block_write_begin fs/buffer.c:2041 [inline] block_write_begin+0x96/0x1e0 fs/buffer.c:2102 cont_write_begin+0x5ea/0x800 fs/buffer.c:2456 hfs_write_begin+0x87/0xd0 fs/hfs/inode.c:58 generic_perform_write+0x2fa/0x5c0 mm/filemap.c:3862 __generic_file_write_iter+0x148/0x2a0 mm/filemap.c:3960 generic_file_write_iter+0xab/0x2e0 mm/filemap.c:3989 call_write_iter include/linux/fs.h:2265 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x4b1/0xa30 fs/read_write.c:584 ksys_write+0x14c/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&tree->tree_lock#2/1){+.+.}-{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+0x2d07/0x7d10 kernel/locking/lockdep.c:5049 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x12d/0xaf0 kernel/locking/mutex.c:747 hfs_find_init+0x15b/0x1d0 fs/hfs/bfind.c:-1 hfs_ext_read_extent fs/hfs/extent.c:200 [inline] hfs_extend_file+0x35d/0x13f0 fs/hfs/extent.c:401 hfs_bmap_reserve+0x103/0x420 fs/hfs/btree.c:234 hfs_cat_create+0x204/0x8e0 fs/hfs/catalog.c:104 hfs_create+0x62/0xd0 fs/hfs/dir.c:202 vfs_create+0x2db/0x460 fs/namei.c:3192 do_mknodat+0x3a1/0x4d0 fs/namei.c:4043 __do_sys_mknod fs/namei.c:4076 [inline] __se_sys_mknod fs/namei.c:4074 [inline] __x64_sys_mknod+0x8a/0xa0 fs/namei.c:4074 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&HFS_I(tree->inode)->extents_lock); lock(&tree->tree_lock#2/1); lock(&HFS_I(tree->inode)->extents_lock); lock(&tree->tree_lock#2/1); *** DEADLOCK *** 4 locks held by syz.5.4671/25398: #0: ffff888076b6a460 (sb_writers#40){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402 #1: ffff8880625d5728 (&type->i_mutex_dir_key#26/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #1: ffff8880625d5728 (&type->i_mutex_dir_key#26/1){+.+.}-{3:3}, at: filename_create+0x208/0x470 fs/namei.c:3884 #2: ffff8880552140b0 (&tree->tree_lock#2){+.+.}-{3:3}, at: hfs_find_init+0x15b/0x1d0 fs/hfs/bfind.c:-1 #3: ffff8880625d4ef8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0xfb/0x13f0 fs/hfs/extent.c:397 stack backtrace: CPU: 1 PID: 25398 Comm: syz.5.4671 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026 Call Trace: dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106 check_noncircular+0x296/0x330 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+0x2d07/0x7d10 kernel/locking/lockdep.c:5049 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x12d/0xaf0 kernel/locking/mutex.c:747 hfs_find_init+0x15b/0x1d0 fs/hfs/bfind.c:-1 hfs_ext_read_extent fs/hfs/extent.c:200 [inline] hfs_extend_file+0x35d/0x13f0 fs/hfs/extent.c:401 hfs_bmap_reserve+0x103/0x420 fs/hfs/btree.c:234 hfs_cat_create+0x204/0x8e0 fs/hfs/catalog.c:104 hfs_create+0x62/0xd0 fs/hfs/dir.c:202 vfs_create+0x2db/0x460 fs/namei.c:3192 do_mknodat+0x3a1/0x4d0 fs/namei.c:4043 __do_sys_mknod fs/namei.c:4076 [inline] __se_sys_mknod fs/namei.c:4074 [inline] __x64_sys_mknod+0x8a/0xa0 fs/namei.c:4074 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f944979bf79 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f944a72f028 EFLAGS: 00000246 ORIG_RAX: 0000000000000085 RAX: ffffffffffffffda RBX: 00007f9449a15fa0 RCX: 00007f944979bf79 RDX: 000000000000070b RSI: 0000000000000000 RDI: 0000200000000000 RBP: 00007f94498327e0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f9449a16038 R14: 00007f9449a15fa0 R15: 00007ffc930bb148