and is ignored by this kernel. Remove the mand
         option from the mount to silence this warning.
=======================================================
============================================
WARNING: possible recursive locking detected
6.9.0-rc7-syzkaller-00023-g6d7ddd805123 #0 Not tainted
--------------------------------------------
syz-executor249/5084 is trying to acquire lock:
ffff888022731548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x383/0x14f0 fs/hfsplus/extents.c:260

but task is already holding lock:
ffff8880227307c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x21b/0x1b70 fs/hfsplus/extents.c:457

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&HFSPLUS_I(inode)->extents_lock);
  lock(&HFSPLUS_I(inode)->extents_lock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

7 locks held by syz-executor249/5084:
 #0: ffff888022498420 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:409
 #1: ffff888022731e00 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:830 [inline]
 #1: ffff888022731e00 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x260/0x540 fs/namei.c:3892
 #2: ffff88807c3e0300 (&sb->s_type->i_mutex_key#15){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:795 [inline]
 #2: ffff88807c3e0300 (&sb->s_type->i_mutex_key#15){+.+.}-{3:3}, at: vfs_link+0x3b3/0x690 fs/namei.c:4596
 #3: ffff888017f55198 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_link+0x237/0x800 fs/hfsplus/dir.c:316
 #4: ffff88802307c0b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x14a/0x1c0
 #5: ffff8880227307c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x21b/0x1b70 fs/hfsplus/extents.c:457
 #6: ffff888017f550f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_allocate+0x9e/0x8c0 fs/hfsplus/bitmap.c:35

stack backtrace:
CPU: 0 PID: 5084 Comm: syz-executor249 Not tainted 6.9.0-rc7-syzkaller-00023-g6d7ddd805123 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain+0x15c1/0x58e0 kernel/locking/lockdep.c:3856
 __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754
 __mutex_lock_common kernel/locking/mutex.c:608 [inline]
 __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752
 hfsplus_get_block+0x383/0x14f0 fs/hfsplus/extents.c:260
 block_read_full_folio+0x430/0xe10 fs/buffer.c:2384
 filemap_read_folio+0x1a2/0x790 mm/filemap.c:2331
 do_read_cache_folio+0x134/0x820 mm/filemap.c:3747
 do_read_cache_page+0x30/0x200 mm/filemap.c:3813
 read_mapping_page include/linux/pagemap.h:888 [inline]
 hfsplus_block_allocate+0xee/0x8c0 fs/hfsplus/bitmap.c:37
 hfsplus_file_extend+0xade/0x1b70 fs/hfsplus/extents.c:468
 hfsplus_bmap_reserve+0x105/0x4e0 fs/hfsplus/btree.c:358
 hfsplus_rename_cat+0x1d0/0x1050 fs/hfsplus/catalog.c:456
 hfsplus_link+0x3ab/0x800 fs/hfsplus/dir.c:323
 vfs_link+0x4f7/0x690 fs/namei.c:4605
 do_linkat+0x356/0x760 fs/namei.c:4676
 __do_sys_link fs/namei.c:4710 [inline]
 __se_sys_link fs/namei.c:4708 [inline]
 __x64_sys_link+0x86/0xa0 fs/namei.c:4708
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0ce9e86779
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc9b6d26d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000056
RAX: ffffffffffffffda RBX: 00007ffc9b6d28b8 RCX: 00007f0ce9e86779
RDX: 0000000000000000 RSI: 0000000020000bc0 RDI: 0000000020000100
RBP: 00007f0ce9efa610 R08: 0