loop0: detected capacity change from 0 to 1024 ============================================ WARNING: possible recursive locking detected 6.8.0-rc5-syzkaller #0 Not tainted -------------------------------------------- syz-executor.0/5435 is trying to acquire lock: ffff88802bee0e88 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_get_block+0x383/0x14e0 fs/hfsplus/extents.c:260 but task is already holding lock: ffff88802bee1c08 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x21b/0x1b70 fs/hfsplus/extents.c:457 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-executor.0/5435: #0: ffff888028602d48 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x258/0x320 fs/file.c:1191 #1: ffff888077c38420 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2794 [inline] #1: ffff888077c38420 (sb_writers#13){.+.+}-{0:0}, at: vfs_write+0x233/0xca0 fs/read_write.c:586 #2: ffff88802bee1e00 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline] #2: ffff88802bee1e00 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: generic_file_write_iter+0x83/0x310 mm/filemap.c:4048 #3: ffff88802bee1c08 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x21b/0x1b70 fs/hfsplus/extents.c:457 #4: ffff88802d3750f8 (&sbi->alloc_mutex){+.+.}-{3:3}, at: hfsplus_block_allocate+0x9e/0x8b0 fs/hfsplus/bitmap.c:35 stack backtrace: CPU: 0 PID: 5435 Comm: syz-executor.0 Not tainted 6.8.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 check_deadlock kernel/locking/lockdep.c:3062 [inline] validate_chain kernel/locking/lockdep.c:3856 [inline] __lock_acquire+0x6aa3/0x7fb0 kernel/locking/lockdep.c:5137 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5754 __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:752 hfsplus_get_block+0x383/0x14e0 fs/hfsplus/extents.c:260 block_read_full_folio+0x422/0xe10 fs/buffer.c:2382 filemap_read_folio+0x19c/0x770 mm/filemap.c:2324 do_read_cache_folio+0x134/0x810 mm/filemap.c:3703 do_read_cache_page+0x30/0x1f0 mm/filemap.c:3769 read_mapping_page include/linux/pagemap.h:888 [inline] hfsplus_block_allocate+0xee/0x8b0 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0xade/0x1b70 fs/hfsplus/extents.c:468 hfsplus_get_block+0x406/0x14e0 fs/hfsplus/extents.c:245 get_more_blocks fs/direct-io.c:647 [inline] do_direct_IO fs/direct-io.c:935 [inline] __blockdev_direct_IO+0x1d65/0x49a0 fs/direct-io.c:1248 blockdev_direct_IO include/linux/fs.h:3117 [inline] hfsplus_direct_IO+0xf8/0x1e0 fs/hfsplus/inode.c:130 generic_file_direct_write+0x1e3/0x3f0 mm/filemap.c:3855 __generic_file_write_iter+0x125/0x230 mm/filemap.c:4011 generic_file_write_iter+0xaf/0x310 mm/filemap.c:4051 call_write_iter include/linux/fs.h:2087 [inline] new_sync_write fs/read_write.c:497 [inline] vfs_write+0xa74/0xca0 fs/read_write.c:590 ksys_write+0x1a0/0x2c0 fs/read_write.c:643 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x85/0x160 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b RIP: 0033:0x7f487887dda9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f48796ca0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f48789abf80 RCX: 00007f487887dda9 RDX: 000000000003fe00 RSI: 0000000020004200 RDI: 0000000000000004 RBP: 00007f48788ca47a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f48789abf80 R15: 00007fff8f08bd28