syzbot

loop0: detected capacity change from 0 to 1024
============================================
WARNING: possible recursive locking detected
5.15.111-syzkaller #0 Not tainted
--------------------------------------------
syz-executor359/3961 is trying to acquire lock:
ffff0000c89a1548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x2c4/0x1194 fs/hfsplus/extents.c:260

but task is already holding lock:
ffff0000c89a2988 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x198/0x14e0 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

4 locks held by syz-executor359/3961:
 #0: ffff0000c8d94460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x228/0xb3c fs/read_write.c:590
 #1: ffff0000c89a2b80 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff0000c89a2b80 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: generic_file_write_iter+0x84/0x1b8 mm/filemap.c:3932
 #2: ffff0000c89a2988 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x198/0x14e0 fs/hfsplus/extents.c:457
 #3: ffff0000c89c38f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_allocate+0x8c/0x800 fs/hfsplus/bitmap.c:35

stack backtrace:
CPU: 1 PID: 3961 Comm: syz-executor359 Not tainted 5.15.111-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Call trace:
 dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 dump_stack+0x1c/0x58 lib/dump_stack.c:113
 __lock_acquire+0x62b4/0x7620 kernel/locking/lockdep.c:5011
 lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5622
 __mutex_lock_common+0x194/0x2154 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
 hfsplus_get_block+0x2c4/0x1194 fs/hfsplus/extents.c:260
 block_read_full_page+0x2a0/0xc4c fs/buffer.c:2290
 hfsplus_readpage+0x28/0x38 fs/hfsplus/inode.c:28
 do_read_cache_page+0x60c/0x950
 read_cache_page+0x68/0x84 mm/filemap.c:3565
 read_mapping_page include/linux/pagemap.h:515 [inline]
 hfsplus_block_allocate+0xe0/0x800 fs/hfsplus/bitmap.c:37
 hfsplus_file_extend+0x770/0x14e0 fs/hfsplus/extents.c:468
 hfsplus_get_block+0x398/0x1194 fs/hfsplus/extents.c:245
 __block_write_begin_int+0x3ec/0x1608 fs/buffer.c:2012
 __block_write_begin fs/buffer.c:2062 [inline]
 block_write_begin fs/buffer.c:2122 [inline]
 cont_write_begin+0x538/0x710 fs/buffer.c:2471
 hfsplus_write_begin+0xa8/0xf8 fs/hfsplus/inode.c:53
 generic_perform_write+0x24c/0x520 mm/filemap.c:3776
 __generic_file_write_iter+0x230/0x454 mm/filemap.c:3903
 generic_file_write_iter+0xb4/0x1b8 mm/filemap.c:3935
 call_write_iter include/linux/fs.h:2103 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0x87c/0xb3c fs/read_write.c:594
 ksys_write+0x15c/0x26c fs/read_write.c:647
 __do_sys_write fs/read_write.c:659 [inline]
 __se_sys_write fs/read_write.c:656 [inline]
 __arm64_sys_write+0x7c/0x90 fs/read_write.c:656
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584