syz-executor239[5031]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
loop0: detected capacity change from 0 to 1024
============================================
WARNING: possible recursive locking detected
6.6.0-rc6-syzkaller-00334-g1acfd2bd3f0d #0 Not tainted
--------------------------------------------
syz-executor239/5031 is trying to acquire lock:
ffff88802026c0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x14a/0x1c0

but task is already holding lock:
ffff88802026c0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x14a/0x1c0

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

       CPU0
       ----
  lock(&tree->tree_lock/1);
  lock(&tree->tree_lock/1);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

5 locks held by syz-executor239/5031:
 #0: ffff888020268410 (sb_writers#9){.+.+}-{0:0}, at: vfs_write+0x216/0xaf0 fs/read_write.c:580
 #1: ffff888076fe8300 (&sb->s_type->i_mutex_key#14){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:802 [inline]
 #1: ffff888076fe8300 (&sb->s_type->i_mutex_key#14){+.+.}-{3:3}, at: generic_file_write_iter+0x83/0x310 mm/filemap.c:4087
 #2: ffff888076fe8108 (&hip->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x21b/0x1b70 fs/hfsplus/extents.c:457
 #3: ffff88802026c0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x14a/0x1c0
 #4: ffff888079328108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x21b/0x1b70 fs/hfsplus/extents.c:457

stack backtrace:
CPU: 0 PID: 5031 Comm: syz-executor239 Not tainted 6.6.0-rc6-syzkaller-00334-g1acfd2bd3f0d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain kernel/locking/lockdep.c:3855 [inline]
 __lock_acquire+0x6a81/0x7f70 kernel/locking/lockdep.c:5136
 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5753
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747
 hfsplus_find_init+0x14a/0x1c0
 hfsplus_ext_read_extent fs/hfsplus/extents.c:216 [inline]
 hfsplus_file_extend+0x454/0x1b70 fs/hfsplus/extents.c:461
 hfsplus_bmap_reserve+0x105/0x4e0 fs/hfsplus/btree.c:358
 __hfsplus_ext_write_extent+0x2a4/0x5b0 fs/hfsplus/extents.c:104
 __hfsplus_ext_cache_extent+0x84/0xe00 fs/hfsplus/extents.c:186
 hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline]
 hfsplus_file_extend+0x48c/0x1b70 fs/hfsplus/extents.c:461
 hfsplus_get_block+0x406/0x14e0 fs/hfsplus/extents.c:245
 __block_write_begin_int+0x54d/0x1ac0 fs/buffer.c:2120
 __block_write_begin fs/buffer.c:2169 [inline]
 block_write_begin+0x9b/0x1e0 fs/buffer.c:2228
 cont_write_begin+0x643/0x880 fs/buffer.c:2585
 hfsplus_write_begin+0x8a/0xd0 fs/hfsplus/inode.c:52
 generic_perform_write+0x31b/0x630 mm/filemap.c:3969
 generic_file_write_iter+0xaf/0x310 mm/filemap.c:4090
 call_write_iter include/linux/fs.h:1956 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x782/0xaf0 fs/read_write.c:584
 ksys_write+0x1a0/0x2c0 fs/read_write.c:637
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fca63813639
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:00007ffde25b29a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007ffde25b2b78 RCX: 00007fca63813639
RDX: 00000000fffffff0 RSI: 0000000020004200 RDI: 0000000000000004
RBP: 00007fca63886610 R08: 0000000000000000 R09: 00007ffde25b2b78
R10: 0000000000000647 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffde25b2b68 R14: 0000000000000001 R15: 0000000000000001
 </TASK>