loop4: detected capacity change from 0 to 1024 ============================================ WARNING: possible recursive locking detected syzkaller #0 Not tainted -------------------------------------------- syz.4.3791/21586 is trying to acquire lock: ffff88804a3f8108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_get_block+0x398/0x15d0 fs/hfsplus/extents.c:260 but task is already holding lock: ffff88804a3fb048 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1f8/0x1ba0 fs/hfsplus/extents.c:453 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 5 locks held by syz.4.3791/21586: #0: ffff888031e7c0e0 (&type->s_umount_key#105/1){+.+.}-{4:4}, at: alloc_super+0x1bb/0x930 fs/super.c:344 #1: ffff888060f68198 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_fill_super+0x1278/0x1b50 fs/hfsplus/super.c:573 #2: ffff8880319fa0b0 (&tree->tree_lock#2){+.+.}-{4:4}, at: hfsplus_find_init+0x168/0x290 fs/hfsplus/bfind.c:28 #3: ffff88804a3fb048 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1f8/0x1ba0 fs/hfsplus/extents.c:453 #4: ffff888060f680f8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_allocate+0xa7/0xc40 fs/hfsplus/bitmap.c:35 stack backtrace: CPU: 1 UID: 0 PID: 21586 Comm: syz.4.3791 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_deadlock_bug+0x28b/0x2a0 kernel/locking/lockdep.c:3041 check_deadlock kernel/locking/lockdep.c:3093 [inline] validate_chain+0x1a3f/0x2140 kernel/locking/lockdep.c:3895 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/mutex.c:598 [inline] __mutex_lock+0x187/0x1350 kernel/locking/mutex.c:760 hfsplus_get_block+0x398/0x15d0 fs/hfsplus/extents.c:260 block_read_full_folio+0x29f/0x830 fs/buffer.c:2420 filemap_read_folio+0x117/0x380 mm/filemap.c:2444 do_read_cache_folio+0x350/0x590 mm/filemap.c:4024 do_read_cache_page mm/filemap.c:4090 [inline] read_cache_page+0x5d/0x170 mm/filemap.c:4099 read_mapping_page include/linux/pagemap.h:993 [inline] hfsplus_block_allocate+0xf3/0xc40 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xa9a/0x1ba0 fs/hfsplus/extents.c:464 hfsplus_bmap_reserve+0x122/0x500 fs/hfsplus/btree.c:358 hfsplus_create_cat+0x18e/0x1120 fs/hfsplus/catalog.c:272 hfsplus_fill_super+0x12f5/0x1b50 fs/hfsplus/super.c:580 get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1691 vfs_get_tree+0x92/0x2b0 fs/super.c:1751 fc_mount fs/namespace.c:1208 [inline] do_new_mount_fc fs/namespace.c:3651 [inline] do_new_mount+0x302/0xa10 fs/namespace.c:3727 do_mount fs/namespace.c:4050 [inline] __do_sys_mount fs/namespace.c:4238 [inline] __se_sys_mount+0x313/0x410 fs/namespace.c:4215 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f79c099076a Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007f79c17c6e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007f79c17c6ef0 RCX: 00007f79c099076a RDX: 000020000009df00 RSI: 0000200000002900 RDI: 00007f79c17c6eb0 RBP: 000020000009df00 R08: 00007f79c17c6ef0 R09: 0000000000008000 R10: 0000000000008000 R11: 0000000000000246 R12: 0000200000002900 R13: 00007f79c17c6eb0 R14: 00000000000006f0 R15: 00002000000022c0 loop4: detected capacity change from 0 to 1024 loop4: detected capacity change from 0 to 2048 hpfs: filesystem error: improperly stopped; already mounted read-only hpfs: filesystem error: warning: spare dnodes used, try chkdsk hpfs: filesystem error: sector(s) 'dir_band_bitmap' badly placed at 00000000