WARNING: The mand mount option has been deprecated and
         and is ignored by this kernel. Remove the mand
         option from the mount to silence this warning.
=======================================================
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.17/4442 is trying to acquire lock:
ffff888060f01548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x3a1/0x15a0 fs/hfsplus/extents.c:260

but task is already holding lock:
ffff888060f007c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1cd/0x1a50 fs/hfsplus/extents.c:455

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.0.17/4442:
 #0: ffff8880746dc460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:386
 #1: ffff888060f01e00 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
 #1: ffff888060f01e00 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: filename_create+0x208/0x470 fs/namei.c:3843
 #2: ffff888060f02b80 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #2: ffff888060f02b80 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: vfs_link+0x513/0x7c0 fs/namei.c:4556
 #3: ffff88802363f998 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_link+0x23a/0x730 fs/hfsplus/dir.c:316
 #4: ffff8880792f60b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28
 #5: ffff888060f007c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1cd/0x1a50 fs/hfsplus/extents.c:455
 #6: ffff88802363f8f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_allocate+0x93/0x910 fs/hfsplus/bitmap.c:35

stack backtrace:
CPU: 0 PID: 4442 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 __lock_acquire+0x1236/0x7d10 kernel/locking/lockdep.c:-1
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1e3/0x2400 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 hfsplus_get_block+0x3a1/0x15a0 fs/hfsplus/extents.c:260
 block_read_full_page+0x306/0xd40 fs/buffer.c:2290
 do_read_cache_page+0x8a1/0x1030 mm/filemap.c:-1
 read_mapping_page include/linux/pagemap.h:515 [inline]
 hfsplus_block_allocate+0xf1/0x910 fs/hfsplus/bitmap.c:37
 hfsplus_file_extend+0xb1f/0x1a50 fs/hfsplus/extents.c:466
 hfsplus_bmap_reserve+0x11e/0x4f0 fs/hfsplus/btree.c:357
 hfsplus_rename_cat+0x219/0xe90 fs/hfsplus/catalog.c:456
 hfsplus_link+0x380/0x730 fs/hfsplus/dir.c:323
 vfs_link+0x615/0x7c0 fs/namei.c:4565
 do_linkat+0x285/0x860 fs/namei.c:4636
 __do_sys_link fs/namei.c:4670 [inline]
 __se_sys_link fs/namei.c:4668 [inline]
 __x64_sys_link+0x82/0x90 fs/namei.c:4668
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f1964127819
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:00007ffd5a7a9068 EFLAGS: 00000246 ORIG_RAX: 0000000000000056
RAX: ffffffffffffffda RBX: 00007f19643a0fa0 RCX: 00007f1964127819
RDX: 0000000000000000 RSI: 0000200000000bc0 RDI: 0000200000000100
RBP: 00007f19641bdc91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f19643a0fac R14: 00007f19643a0fa0 R15: 00007f19643a0fa0
 </TASK>