Warning: Permanently added '10.128.10.56' (ED25519) to the list of known hosts.
executing program
[   44.566232][ T4018] loop0: detected capacity change from 0 to 1024
[   44.677583][ T4018] 
[   44.678273][ T4018] ============================================
[   44.679904][ T4018] WARNING: possible recursive locking detected
[   44.681669][ T4018] 5.15.178-syzkaller #0 Not tainted
[   44.683151][ T4018] --------------------------------------------
[   44.684788][ T4018] syz-executor327/4018 is trying to acquire lock:
[   44.686691][ T4018] ffff0000ca969548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x2c4/0x1194
[   44.689884][ T4018] 
[   44.689884][ T4018] but task is already holding lock:
[   44.691909][ T4018] ffff0000ca96a988 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x250/0xa2c
[   44.695092][ T4018] 
[   44.695092][ T4018] other info that might help us debug this:
[   44.697392][ T4018]  Possible unsafe locking scenario:
[   44.697392][ T4018] 
[   44.699408][ T4018]        CPU0
[   44.700292][ T4018]        ----
[   44.701272][ T4018]   lock(&HFSPLUS_I(inode)->extents_lock);
[   44.702844][ T4018]   lock(&HFSPLUS_I(inode)->extents_lock);
[   44.704522][ T4018] 
[   44.704522][ T4018]  *** DEADLOCK ***
[   44.704522][ T4018] 
[   44.706885][ T4018]  May be due to missing lock nesting notation
[   44.706885][ T4018] 
[   44.709124][ T4018] 6 locks held by syz-executor327/4018:
[   44.710731][ T4018]  #0: ffff0000caed8460 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c
[   44.713255][ T4018]  #1: ffff0000ca969e00 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: do_unlinkat+0x2d0/0x830
[   44.716058][ T4018]  #2: ffff0000ca96ab80 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: vfs_unlink+0xd8/0x508
[   44.718999][ T4018]  #3: ffff0000dac99998 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_unlink+0x144/0x6a0
[   44.721599][ T4018]  #4: ffff0000ca96a988 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x250/0xa2c
[   44.724793][ T4018]  #5: ffff0000dac998f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_free+0xcc/0x514
[   44.727623][ T4018] 
[   44.727623][ T4018] stack backtrace:
[   44.729193][ T4018] CPU: 0 PID: 4018 Comm: syz-executor327 Not tainted 5.15.178-syzkaller #0
[   44.731706][ T4018] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
[   44.734566][ T4018] Call trace:
[   44.735485][ T4018]  dump_backtrace+0x0/0x530
[   44.736772][ T4018]  show_stack+0x2c/0x3c
[   44.737893][ T4018]  dump_stack_lvl+0x108/0x170
[   44.739189][ T4018]  dump_stack+0x1c/0x58
[   44.740419][ T4018]  __lock_acquire+0x62bc/0x7638
[   44.741755][ T4018]  lock_acquire+0x240/0x77c
[   44.743159][ T4018]  __mutex_lock_common+0x194/0x2154
[   44.744537][ T4018]  mutex_lock_nested+0xa4/0xf8
[   44.745817][ T4018]  hfsplus_get_block+0x2c4/0x1194
[   44.747156][ T4018]  block_read_full_page+0x2a0/0xc4c
[   44.748655][ T4018]  hfsplus_readpage+0x28/0x38
[   44.749878][ T4018]  do_read_cache_page+0x60c/0x950
[   44.751392][ T4018]  read_cache_page+0x68/0x84
[   44.752656][ T4018]  hfsplus_block_free+0x120/0x514
[   44.754039][ T4018]  hfsplus_free_extents+0x148/0x8d4
[   44.755468][ T4018]  hfsplus_file_truncate+0x678/0xa2c
[   44.756919][ T4018]  hfsplus_delete_inode+0x154/0x200
[   44.758368][ T4018]  hfsplus_unlink+0x414/0x6a0
[   44.759669][ T4018]  vfs_unlink+0x2f0/0x508
[   44.760896][ T4018]  do_unlinkat+0x4cc/0x830
[   44.762146][ T4018]  __arm64_sys_unlinkat+0xcc/0xfc
[   44.763507][ T4018]  invoke_syscall+0x98/0x2b8
[   44.764687][ T4018]  el0_svc_common+0x138/0x258
[   44.765914][ T4018]  do_el0_svc+0x58/0x14c
[   44.767040][ T4018]  el0_svc+0x7c/0x1f0
[   44.768122][ T4018]  el0t_64_sync_handler+0x84/0xe4
[   44.769508][ T4018]  el0t_64_sync+0x1a0/0x1a4
[   44.771715][ T4018] hfsplus: unable to mark blocks free: error -5
[   44.773617][ T4018] hfsplus: can't free extent