======================================================
WARNING: possible circular locking dependency detected
6.12.0-rc2-syzkaller-00320-gba01565ced22 #0 Not tainted
------------------------------------------------------
syz.5.4266/17197 is trying to acquire lock:
ffff88807fb040b0 (&tree->tree_lock#2/1){+.+.}-{3:3}, at: hfsplus_find_init+0x14a/0x1c0 fs/hfsplus/bfind.c:28

but task is already holding lock:
ffff88807e221548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x383/0x14f0 fs/hfsplus/extents.c:260

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
       __mutex_lock_common kernel/locking/mutex.c:608 [inline]
       __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752
       hfsplus_file_extend+0x21b/0x1b70 fs/hfsplus/extents.c:458
       hfsplus_bmap_reserve+0x105/0x4e0 fs/hfsplus/btree.c:358
       __hfsplus_ext_write_extent+0x2a4/0x5c0 fs/hfsplus/extents.c:104
       __hfsplus_ext_cache_extent+0x84/0xe10 fs/hfsplus/extents.c:186
       hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
       hfsplus_file_extend+0x48c/0x1b70 fs/hfsplus/extents.c:462
       hfsplus_get_block+0x406/0x14f0 fs/hfsplus/extents.c:245
       __block_write_begin_int+0x50e/0x1a70 fs/buffer.c:2121
       block_write_begin fs/buffer.c:2231 [inline]
       cont_write_begin+0x6e2/0x9d0 fs/buffer.c:2582
       hfsplus_write_begin+0x68/0xb0 fs/hfsplus/inode.c:46
       generic_perform_write+0x346/0x6d0 mm/filemap.c:4054
       generic_file_write_iter+0xae/0x310 mm/filemap.c:4181
       new_sync_write fs/read_write.c:590 [inline]
       vfs_write+0xa6f/0xc90 fs/read_write.c:683
       ksys_write+0x183/0x2b0 fs/read_write.c:736
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&tree->tree_lock#2/1){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3161 [inline]
       check_prevs_add kernel/locking/lockdep.c:3280 [inline]
       validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
       __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5202
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
       __mutex_lock_common kernel/locking/mutex.c:608 [inline]
       __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752
       hfsplus_find_init+0x14a/0x1c0 fs/hfsplus/bfind.c:28
       hfsplus_ext_read_extent fs/hfsplus/extents.c:216 [inline]
       hfsplus_get_block+0x5c4/0x14f0 fs/hfsplus/extents.c:268
       generic_block_bmap+0x13c/0x1f0 fs/buffer.c:2759
       bmap+0xaa/0xe0 fs/inode.c:1928
       ioctl_fibmap fs/ioctl.c:77 [inline]
       file_ioctl fs/ioctl.c:328 [inline]
       do_vfs_ioctl+0x2284/0x2e40 fs/ioctl.c:886
       __do_sys_ioctl fs/ioctl.c:905 [inline]
       __se_sys_ioctl+0x81/0x170 fs/ioctl.c:893
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&HFSPLUS_I(inode)->extents_lock);
                               lock(&tree->tree_lock#2/1);
                               lock(&HFSPLUS_I(inode)->extents_lock);
  lock(&tree->tree_lock#2/1);

 *** DEADLOCK ***

1 lock held by syz.5.4266/17197:
 #0: ffff88807e221548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x383/0x14f0 fs/hfsplus/extents.c:260

stack backtrace:
CPU: 0 UID: 0 PID: 17197 Comm: syz.5.4266 Not tainted 6.12.0-rc2-syzkaller-00320-gba01565ced22 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074
 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2206
 check_prev_add kernel/locking/lockdep.c:3161 [inline]
 check_prevs_add kernel/locking/lockdep.c:3280 [inline]
 validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904
 __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5202
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
 __mutex_lock_common kernel/locking/mutex.c:608 [inline]
 __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752
 hfsplus_find_init+0x14a/0x1c0 fs/hfsplus/bfind.c:28
 hfsplus_ext_read_extent fs/hfsplus/extents.c:216 [inline]
 hfsplus_get_block+0x5c4/0x14f0 fs/hfsplus/extents.c:268
 generic_block_bmap+0x13c/0x1f0 fs/buffer.c:2759
 bmap+0xaa/0xe0 fs/inode.c:1928
 ioctl_fibmap fs/ioctl.c:77 [inline]
 file_ioctl fs/ioctl.c:328 [inline]
 do_vfs_ioctl+0x2284/0x2e40 fs/ioctl.c:886
 __do_sys_ioctl fs/ioctl.c:905 [inline]
 __se_sys_ioctl+0x81/0x170 fs/ioctl.c:893
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2fcdf7dff9
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:00007f2fcedff038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f2fce135f80 RCX: 00007f2fcdf7dff9
RDX: 00000000200000c0 RSI: 0000000000000001 RDI: 0000000000000004
RBP: 00007f2fcdff0296 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f2fce135f80 R15: 00007ffc9f496268
 </TASK>