loop3: detected capacity change from 0 to 1024 ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Tainted: G L ------------------------------------------------------ syz.3.327/7020 is trying to acquire lock: ffff888034163f80 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_get_block+0x391/0x1610 fs/hfsplus/extents.c:264 but task is already holding lock: ffff888024bc40f0 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_allocate+0xa9/0xd30 fs/hfsplus/bitmap.c:35 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sbi->alloc_mutex){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821 hfsplus_block_allocate+0xa9/0xd30 fs/hfsplus/bitmap.c:35 hfsplus_file_extend+0xb77/0x1df0 fs/hfsplus/extents.c:468 hfsplus_get_block+0x41f/0x1610 fs/hfsplus/extents.c:249 __block_write_begin_int+0x6c1/0x1930 fs/buffer.c:2034 block_write_begin fs/buffer.c:2148 [inline] cont_write_begin+0x71b/0xac0 fs/buffer.c:2510 hfsplus_write_begin+0x126/0x1e0 fs/hfsplus/inode.c:56 cont_expand_zero fs/buffer.c:2471 [inline] cont_write_begin+0x7b2/0xac0 fs/buffer.c:2500 hfsplus_write_begin+0x126/0x1e0 fs/hfsplus/inode.c:56 generic_perform_write+0x2d5/0x8e0 mm/filemap.c:4374 generic_file_write_iter+0xae/0x330 mm/filemap.c:4517 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x612/0xba0 fs/read_write.c:687 ksys_pwrite64 fs/read_write.c:794 [inline] __do_sys_pwrite64 fs/read_write.c:802 [inline] __se_sys_pwrite64 fs/read_write.c:799 [inline] __x64_sys_pwrite64+0x196/0x220 fs/read_write.c:799 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3209 [inline] check_prevs_add kernel/locking/lockdep.c:3328 [inline] validate_chain kernel/locking/lockdep.c:3952 [inline] __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942 __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821 hfsplus_get_block+0x391/0x1610 fs/hfsplus/extents.c:264 block_read_full_folio+0x2db/0x8c0 fs/buffer.c:2312 filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2520 do_read_cache_folio+0x354/0x590 mm/filemap.c:4156 do_read_cache_page mm/filemap.c:4222 [inline] read_cache_page+0x5d/0x170 mm/filemap.c:4231 read_mapping_page include/linux/pagemap.h:1009 [inline] hfsplus_block_allocate+0xf7/0xd30 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xb77/0x1df0 fs/hfsplus/extents.c:468 hfsplus_get_block+0x41f/0x1610 fs/hfsplus/extents.c:249 __block_write_begin_int+0x6c1/0x1930 fs/buffer.c:2034 block_write_begin fs/buffer.c:2148 [inline] cont_write_begin+0x71b/0xac0 fs/buffer.c:2510 hfsplus_write_begin+0x126/0x1e0 fs/hfsplus/inode.c:56 page_symlink+0x27a/0x440 fs/namei.c:6651 hfsplus_symlink+0xd3/0x390 fs/hfsplus/dir.c:478 vfs_symlink+0x18b/0x330 fs/namei.c:5889 filename_symlinkat+0x1cd/0x410 fs/namei.c:5914 __do_sys_symlink fs/namei.c:5941 [inline] __se_sys_symlink+0x4d/0x2b0 fs/namei.c:5937 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->alloc_mutex); lock(&HFSPLUS_I(inode)->extents_lock); lock(&sbi->alloc_mutex); lock(&HFSPLUS_I(inode)->extents_lock); *** DEADLOCK *** locks held by syz.3.327/7020: 5, last CPU#1: #0: ffff88807b102460 (sb_writers#16){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:494 #1: ffff888034164758 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1069 [inline] #1: ffff888034164758 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2939 [inline] #1: ffff888034164758 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2963 [inline] #1: ffff888034164758 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:5170 #2: ffff888024bc4188 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_symlink+0x81/0x390 fs/hfsplus/dir.c:470 #3: ffff888034167180 (&hip->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x21c/0x1df0 fs/hfsplus/extents.c:457 #4: ffff888024bc40f0 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_allocate+0xa9/0xd30 fs/hfsplus/bitmap.c:35 stack backtrace: CPU: 1 UID: 0 PID: 7020 Comm: syz.3.327 Tainted: G L syzkaller #0 PREEMPT(full) Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2087 check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2219 check_prev_add kernel/locking/lockdep.c:3209 [inline] check_prevs_add kernel/locking/lockdep.c:3328 [inline] validate_chain kernel/locking/lockdep.c:3952 [inline] __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942 __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821 hfsplus_get_block+0x391/0x1610 fs/hfsplus/extents.c:264 block_read_full_folio+0x2db/0x8c0 fs/buffer.c:2312 filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2520 do_read_cache_folio+0x354/0x590 mm/filemap.c:4156 do_read_cache_page mm/filemap.c:4222 [inline] read_cache_page+0x5d/0x170 mm/filemap.c:4231 read_mapping_page include/linux/pagemap.h:1009 [inline] hfsplus_block_allocate+0xf7/0xd30 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xb77/0x1df0 fs/hfsplus/extents.c:468 hfsplus_get_block+0x41f/0x1610 fs/hfsplus/extents.c:249 __block_write_begin_int+0x6c1/0x1930 fs/buffer.c:2034 block_write_begin fs/buffer.c:2148 [inline] cont_write_begin+0x71b/0xac0 fs/buffer.c:2510 hfsplus_write_begin+0x126/0x1e0 fs/hfsplus/inode.c:56 page_symlink+0x27a/0x440 fs/namei.c:6651 hfsplus_symlink+0xd3/0x390 fs/hfsplus/dir.c:478 vfs_symlink+0x18b/0x330 fs/namei.c:5889 filename_symlinkat+0x1cd/0x410 fs/namei.c:5914 __do_sys_symlink fs/namei.c:5941 [inline] __se_sys_symlink+0x4d/0x2b0 fs/namei.c:5937 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline] do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f28af79e159 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:00007f28ad9f6028 EFLAGS: 00000246 ORIG_RAX: 0000000000000058 RAX: ffffffffffffffda RBX: 00007f28afa25fa0 RCX: 00007f28af79e159 RDX: 0000000000000000 RSI: 0000200000000380 RDI: 00002000000003c0 RBP: 00007f28af835024 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f28afa26038 R14: 00007f28afa25fa0 R15: 00007fff62815a38