memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=5018 'syz-executor295' loop0: detected capacity change from 0 to 1024 ====================================================== WARNING: possible circular locking dependency detected 6.5.0-rc1-syzkaller-00152-g4b810bf037e5 #0 Not tainted ------------------------------------------------------ syz-executor295/5018 is trying to acquire lock: ffff8880769c87c8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1c5/0xf90 fs/hfsplus/extents.c:457 but task is already holding lock: ffff8880282c20b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x1a2/0x200 fs/hfsplus/bfind.c:30 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&tree->tree_lock){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747 hfsplus_file_truncate+0xecf/0x1120 fs/hfsplus/extents.c:595 hfsplus_setattr+0x1eb/0x310 fs/hfsplus/inode.c:269 notify_change+0x670/0x1160 fs/attr.c:483 do_truncate+0x15c/0x220 fs/open.c:66 handle_truncate fs/namei.c:3295 [inline] do_open fs/namei.c:3640 [inline] path_openat+0x23f1/0x29c0 fs/namei.c:3793 do_filp_open+0x1de/0x430 fs/namei.c:3820 do_sys_openat2+0x176/0x1e0 fs/open.c:1407 __do_sys_openat2+0x1a4/0x2a0 fs/open.c:1463 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3142 [inline] check_prevs_add kernel/locking/lockdep.c:3261 [inline] validate_chain kernel/locking/lockdep.c:3876 [inline] __lock_acquire+0x2e3d/0x5de0 kernel/locking/lockdep.c:5144 lock_acquire kernel/locking/lockdep.c:5761 [inline] lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5726 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747 hfsplus_file_extend+0x1c5/0xf90 fs/hfsplus/extents.c:457 hfsplus_bmap_reserve+0x318/0x410 fs/hfsplus/btree.c:358 hfsplus_rename_cat+0x2ad/0x1240 fs/hfsplus/catalog.c:456 hfsplus_rename+0x118/0x200 fs/hfsplus/dir.c:552 vfs_rename+0x13e0/0x1c30 fs/namei.c:4857 do_renameat2+0xc3c/0xdc0 fs/namei.c:5009 __do_sys_renameat2 fs/namei.c:5042 [inline] __se_sys_renameat2 fs/namei.c:5039 [inline] __x64_sys_renameat2+0xeb/0x130 fs/namei.c:5039 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&tree->tree_lock); lock(&HFSPLUS_I(inode)->extents_lock); lock(&tree->tree_lock); lock(&HFSPLUS_I(inode)->extents_lock); *** DEADLOCK *** 4 locks held by syz-executor295/5018: #0: ffff8880282c4410 (sb_writers#9){.+.+}-{0:0}, at: do_renameat2+0x3d5/0xdc0 fs/namei.c:4943 #1: ffff8880769c9e00 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:806 [inline] #1: ffff8880769c9e00 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: lock_rename fs/namei.c:3042 [inline] #1: ffff8880769c9e00 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: lock_rename fs/namei.c:3039 [inline] #1: ffff8880769c9e00 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: do_renameat2+0xb25/0xdc0 fs/namei.c:4948 #2: ffff88807c8c8300 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: inode_lock_nested include/linux/fs.h:806 [inline] #2: ffff88807c8c8300 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: lock_two_inodes+0x1b2/0x1e0 fs/inode.c:1143 #3: ffff8880282c20b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x1a2/0x200 fs/hfsplus/bfind.c:30 stack backtrace: CPU: 0 PID: 5018 Comm: syz-executor295 Not tainted 6.5.0-rc1-syzkaller-00152-g4b810bf037e5 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106 check_noncircular+0x311/0x3f0 kernel/locking/lockdep.c:2195 check_prev_add kernel/locking/lockdep.c:3142 [inline] check_prevs_add kernel/locking/lockdep.c:3261 [inline] validate_chain kernel/locking/lockdep.c:3876 [inline] __lock_acquire+0x2e3d/0x5de0 kernel/locking/lockdep.c:5144 lock_acquire kernel/locking/lockdep.c:5761 [inline] lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5726 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747 hfsplus_file_extend+0x1c5/0xf90 fs/hfsplus/extents.c:457 hfsplus_bmap_reserve+0x318/0x410 fs/hfsplus/btree.c:358 hfsplus_rename_cat+0x2ad/0x1240 fs/hfsplus/catalog.c:456 hfsplus_rename+0x118/0x200 fs/hfsplus/dir.c:552 vfs_rename+0x13e0/0x1c30 fs/namei.c:4857 do_renameat2+0xc3c/0xdc0 fs/namei.c:5009 __do_sys_renameat2 fs/namei.c:5042 [inline] __se_sys_renameat2 fs/namei.c:5039 [inline] __x64_sys_renameat2+0xeb/0x130 fs/namei.c:5039 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f98705107b9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fffbdad5488 EFLAGS: 00000246 ORIG_RAX: 000000000000013c RAX: fffffffffff