Warning: Permanently added '10.128.0.139' (ED25519) to the list of known hosts.
executing program
[   44.021571][ T4019] loop0: detected capacity change from 0 to 1024
[   44.112681][ T4019] 
[   44.113379][ T4019] ============================================
[   44.114904][ T4019] WARNING: possible recursive locking detected
[   44.116513][ T4019] 5.15.178-syzkaller #0 Not tainted
[   44.117900][ T4019] --------------------------------------------
[   44.119522][ T4019] syz-executor211/4019 is trying to acquire lock:
[   44.121245][ T4019] ffff0000c8d91548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x2c4/0x1194
[   44.124011][ T4019] 
[   44.124011][ T4019] but task is already holding lock:
[   44.125995][ T4019] ffff0000c8d92988 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x250/0xa2c
[   44.128959][ T4019] 
[   44.128959][ T4019] other info that might help us debug this:
[   44.131077][ T4019]  Possible unsafe locking scenario:
[   44.131077][ T4019] 
[   44.133001][ T4019]        CPU0
[   44.133932][ T4019]        ----
[   44.134790][ T4019]   lock(&HFSPLUS_I(inode)->extents_lock);
[   44.136299][ T4019]   lock(&HFSPLUS_I(inode)->extents_lock);
[   44.137905][ T4019] 
[   44.137905][ T4019]  *** DEADLOCK ***
[   44.137905][ T4019] 
[   44.140090][ T4019]  May be due to missing lock nesting notation
[   44.140090][ T4019] 
[   44.142357][ T4019] 6 locks held by syz-executor211/4019:
[   44.143838][ T4019]  #0: ffff0000cbcde460 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c
[   44.146184][ T4019]  #1: ffff0000c8d91e00 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: do_unlinkat+0x2d0/0x830
[   44.149028][ T4019]  #2: ffff0000c8d92b80 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: vfs_unlink+0xd8/0x508
[   44.151692][ T4019]  #3: ffff0000cb923198 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_unlink+0x144/0x6a0
[   44.154312][ T4019]  #4: ffff0000c8d92988 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x250/0xa2c
[   44.157353][ T4019]  #5: ffff0000cb9230f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_free+0xcc/0x514
[   44.160004][ T4019] 
[   44.160004][ T4019] stack backtrace:
[   44.161563][ T4019] CPU: 0 PID: 4019 Comm: syz-executor211 Not tainted 5.15.178-syzkaller #0
[   44.163938][ T4019] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
[   44.166533][ T4019] Call trace:
[   44.167408][ T4019]  dump_backtrace+0x0/0x530
[   44.168591][ T4019]  show_stack+0x2c/0x3c
[   44.169696][ T4019]  dump_stack_lvl+0x108/0x170
[   44.170973][ T4019]  dump_stack+0x1c/0x58
[   44.172131][ T4019]  __lock_acquire+0x62bc/0x7638
[   44.173430][ T4019]  lock_acquire+0x240/0x77c
[   44.174613][ T4019]  __mutex_lock_common+0x194/0x2154
[   44.176046][ T4019]  mutex_lock_nested+0xa4/0xf8
[   44.177334][ T4019]  hfsplus_get_block+0x2c4/0x1194
[   44.178642][ T4019]  block_read_full_page+0x2a0/0xc4c
[   44.179969][ T4019]  hfsplus_readpage+0x28/0x38
[   44.181211][ T4019]  do_read_cache_page+0x60c/0x950
[   44.182508][ T4019]  read_cache_page+0x68/0x84
[   44.183710][ T4019]  hfsplus_block_free+0x120/0x514
[   44.185109][ T4019]  hfsplus_free_extents+0x148/0x8d4
[   44.186491][ T4019]  hfsplus_file_truncate+0x678/0xa2c
[   44.187887][ T4019]  hfsplus_delete_inode+0x154/0x200
[   44.189240][ T4019]  hfsplus_unlink+0x414/0x6a0
[   44.190481][ T4019]  vfs_unlink+0x2f0/0x508
[   44.191622][ T4019]  do_unlinkat+0x4cc/0x830
[   44.192770][ T4019]  __arm64_sys_unlinkat+0xcc/0xfc
[   44.194092][ T4019]  invoke_syscall+0x98/0x2b8
[   44.195354][ T4019]  el0_svc_common+0x138/0x258
[   44.196604][ T4019]  do_el0_svc+0x58/0x14c
[   44.197695][ T4019]  el0_svc+0x7c/0x1f0
[   44.198786][ T4019]  el0t_64_sync_handler+0x84/0xe4
[   44.200181][ T4019]  el0t_64_sync+0x1a0/0x1a4
[   44.201780][ T4019] hfsplus: unable to mark blocks free: error -5
[   44.203515][ T4019] hfsplus: can't free extent