loop0: detected capacity change from 0 to 1024 ============================================ WARNING: possible recursive locking detected syzkaller #0 Not tainted -------------------------------------------- syz.0.17/6619 is trying to acquire lock: ffff888027bc5378 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x21b/0x1dc0 fs/hfsplus/extents.c:455 but task is already holding lock: ffff88802f982df8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x21b/0x1dc0 fs/hfsplus/extents.c:455 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 4 locks held by syz.0.17/6619: #0: ffff8880117d6480 (sb_writers#12){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2724 [inline] #0: ffff8880117d6480 (sb_writers#12){.+.+}-{0:0}, at: vfs_write+0x22d/0xba0 fs/read_write.c:684 #1: ffff88802f983058 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1029 [inline] #1: ffff88802f983058 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}, at: generic_file_write_iter+0x11f/0x690 mm/filemap.c:4465 #2: ffff88802f982df8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x21b/0x1dc0 fs/hfsplus/extents.c:455 #3: ffff888033a780a0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfsplus_find_init+0x168/0x2d0 fs/hfsplus/bfind.c:28 stack backtrace: CPU: 1 UID: 0 PID: 6619 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_deadlock_bug+0x279/0x290 kernel/locking/lockdep.c:3043 check_deadlock kernel/locking/lockdep.c:3095 [inline] validate_chain kernel/locking/lockdep.c:3897 [inline] __lock_acquire+0x253f/0x2cf0 kernel/locking/lockdep.c:5239 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5870 __mutex_lock_common kernel/locking/rtmutex_api.c:534 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:553 hfsplus_file_extend+0x21b/0x1dc0 fs/hfsplus/extents.c:455 hfsplus_bmap_reserve+0x183/0x5b0 fs/hfsplus/btree.c:510 __hfsplus_ext_write_extent+0x2b5/0x6a0 fs/hfsplus/extents.c:104 __hfsplus_ext_cache_extent+0x9b/0x780 fs/hfsplus/extents.c:188 hfsplus_ext_read_extent fs/hfsplus/extents.c:220 [inline] hfsplus_file_extend+0x4ba/0x1dc0 fs/hfsplus/extents.c:459 hfsplus_get_block+0x42e/0x1670 fs/hfsplus/extents.c:247 __block_write_begin_int+0x6c6/0x1910 fs/buffer.c:2042 block_write_begin fs/buffer.c:2153 [inline] cont_write_begin+0x737/0xae0 fs/buffer.c:2491 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:48 cont_expand_zero fs/buffer.c:2419 [inline] cont_write_begin+0x2e7/0xae0 fs/buffer.c:2481 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:48 generic_perform_write+0x2af/0x8b0 mm/filemap.c:4325 generic_file_write_iter+0x14b/0x690 mm/filemap.c:4468 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x629/0xba0 fs/read_write.c:688 ksys_pwrite64 fs/read_write.c:795 [inline] __do_sys_pwrite64 fs/read_write.c:803 [inline] __se_sys_pwrite64 fs/read_write.c:800 [inline] __x64_sys_pwrite64+0x19c/0x230 fs/read_write.c:800 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f73e32faeb9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f73e295e028 EFLAGS: 00000246 ORIG_RAX: 0000000000000012 RAX: ffffffffffffffda RBX: 00007f73e3575fa0 RCX: 00007f73e32faeb9 RDX: 0000000000000001 RSI: 00002000000005c0 RDI: 0000000000000004 RBP: 00007f73e3368c1f R08: 0000000000000000 R09: 0000000000000000 R10: 000000000004fed0 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f73e3576038 R14: 00007f73e3575fa0 R15: 00007ffeac99d8a8