loop6: detected capacity change from 0 to 64 ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.6.798/9140 is trying to acquire lock: ffff8880770dae78 (&HFS_I(tree->inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0xff/0x1380 fs/hfs/extent.c:397 but task is already holding lock: ffff88802d8da0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x17e/0x1f0 fs/hfs/bfind.c:-1 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&tree->tree_lock/1){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xcc0 kernel/locking/mutex.c:747 hfs_find_init+0x17e/0x1f0 fs/hfs/bfind.c:-1 hfs_ext_read_extent fs/hfs/extent.c:200 [inline] hfs_extend_file+0x361/0x1380 fs/hfs/extent.c:401 hfs_bmap_reserve+0x107/0x430 fs/hfs/btree.c:269 hfs_cat_create+0x1fe/0x6b0 fs/hfs/catalog.c:104 hfs_mkdir+0x6c/0xe0 fs/hfs/dir.c:232 vfs_mkdir+0x296/0x440 fs/namei.c:4121 do_mkdirat+0x1dc/0x450 fs/namei.c:4144 __do_sys_mkdirat fs/namei.c:4159 [inline] __se_sys_mkdirat fs/namei.c:4157 [inline] __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4157 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&HFS_I(tree->inode)->extents_lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2df1/0x7d40 kernel/locking/lockdep.c:5137 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xcc0 kernel/locking/mutex.c:747 hfs_extend_file+0xff/0x1380 fs/hfs/extent.c:397 hfs_bmap_reserve+0x107/0x430 fs/hfs/btree.c:269 __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+0x3a0/0x1380 fs/hfs/extent.c:401 hfs_get_block+0x413/0xc50 fs/hfs/extent.c:353 __block_write_begin_int+0x57f/0x1af0 fs/buffer.c:2124 __block_write_begin fs/buffer.c:2173 [inline] block_write_begin+0x9a/0x1e0 fs/buffer.c:2234 cont_write_begin+0x5ee/0x810 fs/buffer.c:2591 hfs_write_begin+0x8b/0xd0 fs/hfs/inode.c:58 generic_perform_write+0x2fe/0x5c0 mm/filemap.c:4031 generic_file_write_iter+0xaf/0x2e0 mm/filemap.c:4152 call_write_iter include/linux/fs.h:2018 [inline] aio_write+0x564/0x7d0 fs/aio.c:1593 __io_submit_one fs/aio.c:-1 [inline] io_submit_one+0x73f/0x12a0 fs/aio.c:2012 __do_sys_io_submit fs/aio.c:2071 [inline] __se_sys_io_submit+0x1a1/0x310 fs/aio.c:2041 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/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(&tree->tree_lock/1); lock(&HFS_I(tree->inode)->extents_lock); lock(&tree->tree_lock/1); lock(&HFS_I(tree->inode)->extents_lock); *** DEADLOCK *** 3 locks held by syz.6.798/9140: #0: ffff8880770dbd38 (&sb->s_type->i_mutex_key#24){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline] #0: ffff8880770dbd38 (&sb->s_type->i_mutex_key#24){+.+.}-{3:3}, at: generic_file_write_iter+0x83/0x2e0 mm/filemap.c:4149 #1: ffff8880770dbb78 (&HFS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0xff/0x1380 fs/hfs/extent.c:397 #2: ffff88802d8da0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x17e/0x1f0 fs/hfs/bfind.c:-1 stack backtrace: CPU: 1 PID: 9140 Comm: syz.6.798 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026 Call Trace: dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106 check_noncircular+0x2fc/0x400 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2df1/0x7d40 kernel/locking/lockdep.c:5137 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xcc0 kernel/locking/mutex.c:747 hfs_extend_file+0xff/0x1380 fs/hfs/extent.c:397 hfs_bmap_reserve+0x107/0x430 fs/hfs/btree.c:269 __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+0x3a0/0x1380 fs/hfs/extent.c:401 hfs_get_block+0x413/0xc50 fs/hfs/extent.c:353 __block_write_begin_int+0x57f/0x1af0 fs/buffer.c:2124 __block_write_begin fs/buffer.c:2173 [inline] block_write_begin+0x9a/0x1e0 fs/buffer.c:2234 cont_write_begin+0x5ee/0x810 fs/buffer.c:2591 hfs_write_begin+0x8b/0xd0 fs/hfs/inode.c:58 generic_perform_write+0x2fe/0x5c0 mm/filemap.c:4031 generic_file_write_iter+0xaf/0x2e0 mm/filemap.c:4152 call_write_iter include/linux/fs.h:2018 [inline] aio_write+0x564/0x7d0 fs/aio.c:1593 __io_submit_one fs/aio.c:-1 [inline] io_submit_one+0x73f/0x12a0 fs/aio.c:2012 __do_sys_io_submit fs/aio.c:2071 [inline] __se_sys_io_submit+0x1a1/0x310 fs/aio.c:2041 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f8e99b9c819 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:00007f8e9aa6a028 EFLAGS: 00000246 ORIG_RAX: 00000000000000d1 RAX: ffffffffffffffda RBX: 00007f8e99e15fa0 RCX: 00007f8e99b9c819 RDX: 0000200000000540 RSI: 000000000000003b RDI: 00007f8e9aa41000 RBP: 00007f8e99c32c91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f8e99e16038 R14: 00007f8e99e15fa0 R15: 00007ffc26cc0068