Warning: Permanently added '10.128.0.101' (ED25519) to the list of known hosts.
executing program
[   43.690697][ T4017] loop0: detected capacity change from 0 to 1024
[   43.788543][ T4017] 
[   43.789197][ T4017] ============================================
[   43.790714][ T4017] WARNING: possible recursive locking detected
[   43.792234][ T4017] 5.15.178-syzkaller #0 Not tainted
[   43.793528][ T4017] --------------------------------------------
[   43.795074][ T4017] syz-executor332/4017 is trying to acquire lock:
[   43.796678][ T4017] ffff0000cbd79548 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x2c4/0x1194
[   43.799606][ T4017] 
[   43.799606][ T4017] but task is already holding lock:
[   43.801544][ T4017] ffff0000cbd7a988 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x250/0xa2c
[   43.804528][ T4017] 
[   43.804528][ T4017] other info that might help us debug this:
[   43.806668][ T4017]  Possible unsafe locking scenario:
[   43.806668][ T4017] 
[   43.808594][ T4017]        CPU0
[   43.809397][ T4017]        ----
[   43.810254][ T4017]   lock(&HFSPLUS_I(inode)->extents_lock);
[   43.811730][ T4017]   lock(&HFSPLUS_I(inode)->extents_lock);
[   43.813180][ T4017] 
[   43.813180][ T4017]  *** DEADLOCK ***
[   43.813180][ T4017] 
[   43.815298][ T4017]  May be due to missing lock nesting notation
[   43.815298][ T4017] 
[   43.817464][ T4017] 6 locks held by syz-executor332/4017:
[   43.818874][ T4017]  #0: ffff0000caa06460 (sb_writers#8){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c
[   43.821273][ T4017]  #1: ffff0000cbd79e00 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: do_unlinkat+0x2d0/0x830
[   43.824065][ T4017]  #2: ffff0000cbd7ab80 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: vfs_unlink+0xd8/0x508
[   43.826760][ T4017]  #3: ffff0000c7bfb198 (&sbi->vh_mutex){+.+.}-{3:3}, at: hfsplus_unlink+0x144/0x6a0
[   43.829231][ T4017]  #4: ffff0000cbd7a988 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_truncate+0x250/0xa2c
[   43.832216][ T4017]  #5: ffff0000c7bfb0f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_free+0xcc/0x514
[   43.834880][ T4017] 
[   43.834880][ T4017] stack backtrace:
[   43.836398][ T4017] CPU: 1 PID: 4017 Comm: syz-executor332 Not tainted 5.15.178-syzkaller #0
[   43.838666][ T4017] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
[   43.841315][ T4017] Call trace:
[   43.842194][ T4017]  dump_backtrace+0x0/0x530
[   43.843403][ T4017]  show_stack+0x2c/0x3c
[   43.844454][ T4017]  dump_stack_lvl+0x108/0x170
[   43.845662][ T4017]  dump_stack+0x1c/0x58
[   43.846780][ T4017]  __lock_acquire+0x62bc/0x7638
[   43.848058][ T4017]  lock_acquire+0x240/0x77c
[   43.849269][ T4017]  __mutex_lock_common+0x194/0x2154
[   43.850563][ T4017]  mutex_lock_nested+0xa4/0xf8
[   43.851813][ T4017]  hfsplus_get_block+0x2c4/0x1194
[   43.853078][ T4017]  block_read_full_page+0x2a0/0xc4c
[   43.854404][ T4017]  hfsplus_readpage+0x28/0x38
[   43.855605][ T4017]  do_read_cache_page+0x60c/0x950
[   43.856866][ T4017]  read_cache_page+0x68/0x84
[   43.858008][ T4017]  hfsplus_block_free+0x120/0x514
[   43.859242][ T4017]  hfsplus_free_extents+0x148/0x8d4
[   43.860569][ T4017]  hfsplus_file_truncate+0x678/0xa2c
[   43.861912][ T4017]  hfsplus_delete_inode+0x154/0x200
[   43.863257][ T4017]  hfsplus_unlink+0x414/0x6a0
[   43.864472][ T4017]  vfs_unlink+0x2f0/0x508
[   43.865546][ T4017]  do_unlinkat+0x4cc/0x830
[   43.866668][ T4017]  __arm64_sys_unlinkat+0xcc/0xfc
[   43.868035][ T4017]  invoke_syscall+0x98/0x2b8
[   43.869266][ T4017]  el0_svc_common+0x138/0x258
[   43.870477][ T4017]  do_el0_svc+0x58/0x14c
[   43.871522][ T4017]  el0_svc+0x7c/0x1f0
[   43.872584][ T4017]  el0t_64_sync_handler+0x84/0xe4
[   43.873866][ T4017]  el0t_64_sync+0x1a0/0x1a4
[   43.875344][ T4017] hfsplus: unable to mark blocks free: error -5
[   43.876931][ T4017] hfsplus: can't free extent