====================================================== WARNING: possible circular locking dependency detected 6.14.0-syzkaller-13423-ga8662bcd2ff1 #0 Not tainted ------------------------------------------------------ syz.0.0/5331 is trying to acquire lock: ffff8880369220b0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfsplus_find_init+0x14f/0x1d0 fs/hfsplus/bfind.c:28 but task is already holding lock: ffff888043947048 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2fa/0xc70 fs/hfsplus/extents.c:577 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}: lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866 __mutex_lock_common kernel/locking/mutex.c:601 [inline] __mutex_lock+0x1a5/0x10c0 kernel/locking/mutex.c:746 hfsplus_file_extend+0x21d/0x1b70 fs/hfsplus/extents.c:458 hfsplus_bmap_reserve+0x105/0x4e0 fs/hfsplus/btree.c:358 __hfsplus_ext_write_extent+0x2a4/0x5c0 fs/hfsplus/extents.c:104 __hfsplus_ext_cache_extent+0x84/0xe10 fs/hfsplus/extents.c:186 hfsplus_ext_read_extent fs/hfsplus/extents.c:218 [inline] hfsplus_file_extend+0x48e/0x1b70 fs/hfsplus/extents.c:462 hfsplus_get_block+0x408/0x14f0 fs/hfsplus/extents.c:245 __block_write_begin_int+0x691/0x1930 fs/buffer.c:2116 block_write_begin fs/buffer.c:2227 [inline] cont_write_begin+0x781/0xb40 fs/buffer.c:2566 hfsplus_write_begin+0x68/0xb0 fs/hfsplus/inode.c:46 generic_perform_write+0x329/0xa10 mm/filemap.c:4102 generic_file_write_iter+0x10e/0x5e0 mm/filemap.c:4245 aio_write+0x56d/0x7d0 fs/aio.c:1633 __io_submit_one fs/aio.c:-1 [inline] io_submit_one+0x8a9/0x18b0 fs/aio.c:2052 __do_sys_io_submit fs/aio.c:2111 [inline] __se_sys_io_submit+0x17a/0x2e0 fs/aio.c:2081 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&tree->tree_lock/1){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xa69/0x24e0 kernel/locking/lockdep.c:3909 __lock_acquire+0xad5/0xd80 kernel/locking/lockdep.c:5235 lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866 __mutex_lock_common kernel/locking/mutex.c:601 [inline] __mutex_lock+0x1a5/0x10c0 kernel/locking/mutex.c:746 hfsplus_find_init+0x14f/0x1d0 fs/hfsplus/bfind.c:28 hfsplus_file_truncate+0x459/0xc70 fs/hfsplus/extents.c:583 hfsplus_delete_inode+0x174/0x220 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x518/0x7b0 fs/hfsplus/dir.c:405 hfsplus_rename+0xc8/0x1c0 fs/hfsplus/dir.c:547 vfs_rename+0xbce/0xf10 fs/namei.c:5086 do_renameat2+0xc8d/0x1290 fs/namei.c:5235 __do_sys_rename fs/namei.c:5282 [inline] __se_sys_rename fs/namei.c:5280 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5280 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf3/0x230 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(&tree->tree_lock/1); lock(&HFSPLUS_I(inode)->extents_lock); lock(&tree->tree_lock/1); *** DEADLOCK *** 6 locks held by syz.0.0/5331: #0: ffff888030f78420 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:556 #1: ffff888043945df8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:902 [inline] #1: ffff888043945df8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: lock_rename fs/namei.c:3230 [inline] #1: ffff888043945df8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: do_renameat2+0x633/0x1290 fs/namei.c:5181 #2: ffff888043946b78 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline] #2: ffff888043946b78 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: lock_two_nondirectories+0xe1/0x170 fs/inode.c:1233 #3: ffff888043947238 (&sb->s_type->i_mutex_key#20/4){+.+.}-{4:4}, at: vfs_rename+0x686/0xf10 fs/namei.c:5057 #4: ffff888043943198 (&sbi->vh_mutex){+.+.}-{4:4}, at: hfsplus_unlink+0x17a/0x7b0 fs/hfsplus/dir.c:370 #5: ffff888043947048 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_truncate+0x2fa/0xc70 fs/hfsplus/extents.c:577 stack backtrace: CPU: 0 UID: 0 PID: 5331 Comm: syz.0.0 Not tainted 6.14.0-syzkaller-13423-ga8662bcd2ff1 #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2079 check_noncircular+0x142/0x160 kernel/locking/lockdep.c:2211 check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xa69/0x24e0 kernel/locking/lockdep.c:3909 __lock_acquire+0xad5/0xd80 kernel/locking/lockdep.c:5235 lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866 __mutex_lock_common kernel/locking/mutex.c:601 [inline] __mutex_lock+0x1a5/0x10c0 kernel/locking/mutex.c:746 hfsplus_find_init+0x14f/0x1d0 fs/hfsplus/bfind.c:28 hfsplus_file_truncate+0x459/0xc70 fs/hfsplus/extents.c:583 hfsplus_delete_inode+0x174/0x220 fs/hfsplus/inode.c:-1 hfsplus_unlink+0x518/0x7b0 fs/hfsplus/dir.c:405 hfsplus_rename+0xc8/0x1c0 fs/hfsplus/dir.c:547 vfs_rename+0xbce/0xf10 fs/namei.c:5086 do_renameat2+0xc8d/0x1290 fs/namei.c:5235 __do_sys_rename fs/namei.c:5282 [inline] __se_sys_rename fs/namei.c:5280 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5280 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fbafa78d169 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fbafb50f038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007fbafa9a6080 RCX: 00007fbafa78d169 RDX: 0000000000000000 RSI: 0000200000000340 RDI: 0000200000000300 RBP: 00007fbafa80e2a0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fbafa9a6080 R15: 00007fff06eaa5a8 netlink: 8 bytes leftover after parsing attributes in process `syz.0.0'. netlink: 8 bytes leftover after parsing attributes in process `syz.0.0'.