============================================ WARNING: possible recursive locking detected 6.15.0-rc5-syzkaller-00136-g9c69f8884904 #0 Not tainted -------------------------------------------- syz.3.421/9562 is trying to acquire lock: ffff88805ce3c488 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_get_block+0x39e/0x1530 fs/hfsplus/extents.c:260 but task is already holding lock: ffff88805ce3e648 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x294/0xb40 fs/hfsplus/extents.c:577 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 6 locks held by syz.3.421/9562: #0: ffff88805e4e4420 (sb_writers#30){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:556 #1: ffff888053622b78 (&type->i_mutex_dir_key#23/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:902 [inline] #1: ffff888053622b78 (&type->i_mutex_dir_key#23/1){+.+.}-{4:4}, at: do_unlinkat+0x1bf/0x560 fs/namei.c:4630 #2: ffff88805ce3e838 (&sb->s_type->i_mutex_key#36){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline] #2: ffff88805ce3e838 (&sb->s_type->i_mutex_key#36){+.+.}-{4:4}, at: vfs_unlink+0xf2/0x650 fs/namei.c:4568 #3: ffff88807a0f4998 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x160/0x730 fs/hfsplus/dir.c:370 #4: ffff88805ce3e648 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x294/0xb40 fs/hfsplus/extents.c:577 #5: ffff88807a0f48f8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xc3/0x4c0 fs/hfsplus/bitmap.c:182 stack backtrace: CPU: 0 UID: 0 PID: 9562 Comm: syz.3.421 Not tainted 6.15.0-rc5-syzkaller-00136-g9c69f8884904 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/29/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_deadlock_bug+0x28b/0x2a0 kernel/locking/lockdep.c:3042 check_deadlock kernel/locking/lockdep.c:3094 [inline] validate_chain+0x1a3f/0x2140 kernel/locking/lockdep.c:3896 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 __mutex_lock_common kernel/locking/mutex.c:601 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:746 hfsplus_get_block+0x39e/0x1530 fs/hfsplus/extents.c:260 block_read_full_folio+0x29c/0x830 fs/buffer.c:2427 filemap_read_folio+0x114/0x380 mm/filemap.c:2401 do_read_cache_folio+0x354/0x590 mm/filemap.c:3885 do_read_cache_page mm/filemap.c:3951 [inline] read_cache_page+0x5d/0x170 mm/filemap.c:3960 read_mapping_page include/linux/pagemap.h:989 [inline] hfsplus_block_free+0x12c/0x4c0 fs/hfsplus/bitmap.c:185 hfsplus_free_extents+0x176/0xae0 fs/hfsplus/extents.c:363 hfsplus_file_truncate+0x736/0xb40 fs/hfsplus/extents.c:592 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4e3/0x730 fs/hfsplus/dir.c:405 vfs_unlink+0x391/0x650 fs/namei.c:4579 do_unlinkat+0x350/0x560 fs/namei.c:4643 __do_sys_unlinkat fs/namei.c:4684 [inline] __se_sys_unlinkat fs/namei.c:4677 [inline] __x64_sys_unlinkat+0xd3/0xf0 fs/namei.c:4677 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fc0bf38e969 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fc0c02bb038 EFLAGS: 00000246 ORIG_RAX: 0000000000000107 RAX: ffffffffffffffda RBX: 00007fc0bf5b5fa0 RCX: 00007fc0bf38e969 RDX: 0000000000000000 RSI: 0000200000000c40 RDI: ffffffffffffff9c RBP: 00007fc0bf410ab1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fc0bf5b5fa0 R15: 00007ffd99eb7118 hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent