loop0: detected capacity change from 0 to 1024 ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/6312 is trying to acquire lock: ffff8880502d98e8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_free+0xc7/0x630 fs/hfsplus/bitmap.c:182 but task is already holding lock: ffff888029d99ef8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2b3/0xc30 fs/hfsplus/extents.c:573 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}: __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552 hfsplus_get_block+0x3a0/0x1670 fs/hfsplus/extents.c:260 block_read_full_folio+0x29f/0x830 fs/buffer.c:2420 filemap_read_folio+0x137/0x3b0 mm/filemap.c:2496 do_read_cache_folio+0x2bf/0x560 mm/filemap.c:4096 do_read_cache_page mm/filemap.c:4162 [inline] read_cache_page+0x5d/0x170 mm/filemap.c:4171 read_mapping_page include/linux/pagemap.h:1022 [inline] hfsplus_block_allocate+0xf3/0xce0 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xb2d/0x1d70 fs/hfsplus/extents.c:464 hfsplus_get_block+0x42e/0x1670 fs/hfsplus/extents.c:245 __block_write_begin_int+0x6c6/0x1910 fs/buffer.c:2145 block_write_begin fs/buffer.c:2256 [inline] cont_write_begin+0x737/0xae0 fs/buffer.c:2594 hfsplus_write_begin+0x66/0xb0 fs/hfsplus/inode.c:48 page_symlink+0x27a/0x440 fs/namei.c:6352 hfsplus_symlink+0xc9/0x290 fs/hfsplus/dir.c:481 vfs_symlink+0x195/0x340 fs/namei.c:5589 do_symlinkat+0x1cd/0x430 fs/namei.c:5616 __do_sys_symlink fs/namei.c:5642 [inline] __se_sys_symlink fs/namei.c:5640 [inline] __x64_sys_symlink+0x7a/0x90 fs/namei.c:5640 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&sbi->alloc_mutex){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552 hfsplus_block_free+0xc7/0x630 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x121/0xa50 fs/hfsplus/extents.c:360 hfsplus_file_truncate+0x762/0xc30 fs/hfsplus/extents.c:588 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4f1/0x930 fs/hfsplus/dir.c:426 hfsplus_rename+0xca/0x1f0 fs/hfsplus/dir.c:591 vfs_rename+0xa96/0xeb0 fs/namei.c:6004 do_renameat2+0x503/0x970 fs/namei.c:6122 __do_sys_renameat2 fs/namei.c:6152 [inline] __se_sys_renameat2 fs/namei.c:6149 [inline] __x64_sys_renameat2+0xce/0xe0 fs/namei.c:6149 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&HFSPLUS_I(inode)->extents_lock); lock(&sbi->alloc_mutex); lock(&HFSPLUS_I(inode)->extents_lock); lock(&sbi->alloc_mutex); *** DEADLOCK *** 6 locks held by syz-executor.0/6312: #0: ffff88803412c480 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493 #1: ffff88804d3719d8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline] #1: ffff88804d3719d8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: lock_rename fs/namei.c:3721 [inline] #1: ffff88804d3719d8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: __start_renaming+0x148/0x410 fs/namei.c:3817 #2: ffff888029d99258 (&sb->s_type->i_mutex_key#22){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1028 [inline] #2: ffff888029d99258 (&sb->s_type->i_mutex_key#22){+.+.}-{4:4}, at: lock_two_nondirectories+0xe7/0x180 fs/inode.c:1251 #3: ffff888029d9a158 (&sb->s_type->i_mutex_key#22/4){+.+.}-{4:4}, at: vfs_rename+0x68a/0xeb0 fs/namei.c:5967 #4: ffff8880502d9978 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x185/0x930 fs/hfsplus/dir.c:391 #5: ffff888029d99ef8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2b3/0xc30 fs/hfsplus/extents.c:573 stack backtrace: CPU: 1 UID: 0 PID: 6312 Comm: syz-executor.0 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043 check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2175 check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552 hfsplus_block_free+0xc7/0x630 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x121/0xa50 fs/hfsplus/extents.c:360 hfsplus_file_truncate+0x762/0xc30 fs/hfsplus/extents.c:588 hfsplus_delete_inode+0x180/0x230 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x4f1/0x930 fs/hfsplus/dir.c:426 hfsplus_rename+0xca/0x1f0 fs/hfsplus/dir.c:591 vfs_rename+0xa96/0xeb0 fs/namei.c:6004 do_renameat2+0x503/0x970 fs/namei.c:6122 __do_sys_renameat2 fs/namei.c:6152 [inline] __se_sys_renameat2 fs/namei.c:6149 [inline] __x64_sys_renameat2+0xce/0xe0 fs/namei.c:6149 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f7eb60ee3b9 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 d0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f7eb547e0b8 EFLAGS: 00000246 ORIG_RAX: 000000000000013c RAX: ffffffffffffffda RBX: 00007f7eb622bf80 RCX: 00007f7eb60ee3b9 RDX: 0000000000000004 RSI: 00000000200000c0 RDI: 0000000000000005 RBP: 00007f7eb614f498 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000020000180 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f7eb622bf80 R15: 00007ffe534c7ed8