====================================================== WARNING: possible circular locking dependency detected 6.2.0-rc7-syzkaller-17907-g2d3827b3f393 #0 Not tainted ------------------------------------------------------ syz-executor.5/6634 is trying to acquire lock: ffff0001116f5ac8 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1122 [inline] ffff0001116f5ac8 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_fallocate+0x5d0/0x904 fs/ntfs3/file.c:568 but task is already holding lock: ffff0001116f5f08 (mapping.invalidate_lock#5){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline] ffff0001116f5f08 (mapping.invalidate_lock#5){++++}-{3:3}, at: ntfs_fallocate+0x218/0x904 fs/ntfs3/file.c:488 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (mapping.invalidate_lock#5){++++}-{3:3}: down_read+0x5c/0x78 kernel/locking/rwsem.c:1509 filemap_invalidate_lock_shared include/linux/fs.h:811 [inline] filemap_fault+0x220/0xaa4 mm/filemap.c:3146 __do_fault+0x74/0x32c mm/memory.c:4163 do_read_fault mm/memory.c:4514 [inline] do_fault mm/memory.c:4643 [inline] handle_pte_fault mm/memory.c:4931 [inline] __handle_mm_fault mm/memory.c:5073 [inline] handle_mm_fault+0x1158/0x241c mm/memory.c:5219 faultin_page mm/gup.c:926 [inline] __get_user_pages+0x26c/0x5f8 mm/gup.c:1153 populate_vma_page_range+0x158/0x1d4 mm/gup.c:1526 __mm_populate+0x154/0x26c mm/gup.c:1640 mm_populate include/linux/mm.h:2874 [inline] vm_mmap_pgoff+0x138/0x1dc mm/util.c:525 ksys_mmap_pgoff+0x1f8/0x278 mm/mmap.c:1457 __do_sys_mmap arch/arm64/kernel/sys.c:28 [inline] __se_sys_mmap arch/arm64/kernel/sys.c:21 [inline] __arm64_sys_mmap+0x58/0x6c arch/arm64/kernel/sys.c:21 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x64/0x178 arch/arm64/kernel/syscall.c:52 el0_svc_common+0xbc/0x180 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x110 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x14c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591 -> #2 (&mm->mmap_lock){++++}-{3:3}: __might_fault+0x7c/0xb4 mm/memory.c:5647 _copy_to_user include/linux/uaccess.h:143 [inline] copy_to_user include/linux/uaccess.h:169 [inline] fiemap_fill_next_extent+0xc4/0x1f8 fs/ioctl.c:144 ni_fiemap+0x4bc/0x610 fs/ntfs3/frecord.c:2061 ntfs_fiemap+0x9c/0xdc fs/ntfs3/file.c:1150 ioctl_fiemap fs/ioctl.c:219 [inline] do_vfs_ioctl+0xfd8/0x1588 fs/ioctl.c:810 __do_sys_ioctl fs/ioctl.c:868 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __arm64_sys_ioctl+0x98/0x148 fs/ioctl.c:856 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x64/0x178 arch/arm64/kernel/syscall.c:52 el0_svc_common+0xbc/0x180 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x110 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x14c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591 -> #1 (&ni->file.run_lock#3){++++}-{3:3}: down_write+0x5c/0x88 kernel/locking/rwsem.c:1562 ntfs_set_size+0xbc/0x150 fs/ntfs3/inode.c:821 ntfs_extend+0xc4/0x27c fs/ntfs3/file.c:337 ntfs_file_write_iter+0x1a4/0x31c fs/ntfs3/file.c:1064 call_write_iter include/linux/fs.h:2189 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x2bc/0x44c fs/read_write.c:584 ksys_write+0xb4/0x160 fs/read_write.c:637 __do_sys_write fs/read_write.c:649 [inline] __se_sys_write fs/read_write.c:646 [inline] __arm64_sys_write+0x24/0x34 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x64/0x178 arch/arm64/kernel/syscall.c:52 el0_svc_common+0xbc/0x180 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x110 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x14c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591 -> #0 (&ni->ni_lock/4){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain kernel/locking/lockdep.c:3831 [inline] __lock_acquire+0x1670/0x2f48 kernel/locking/lockdep.c:5055 lock_acquire+0x164/0x334 kernel/locking/lockdep.c:5668 __mutex_lock_common+0xd4/0xf64 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 ni_lock fs/ntfs3/ntfs_fs.h:1122 [inline] ntfs_fallocate+0x5d0/0x904 fs/ntfs3/file.c:568 vfs_fallocate+0x328/0x388 fs/open.c:323 ksys_fallocate fs/open.c:346 [inline] __do_sys_fallocate fs/open.c:354 [inline] __se_sys_fallocate fs/open.c:352 [inline] __arm64_sys_fallocate+0x5c/0xac fs/open.c:352 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x64/0x178 arch/arm64/kernel/syscall.c:52 el0_svc_common+0xbc/0x180 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x110 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x14c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591 other info that might help us debug this: Chain exists of: &ni->ni_lock/4 --> &mm->mmap_lock --> mapping.invalidate_lock#5 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(mapping.invalidate_lock#5); lock(&mm->mmap_lock); lock(mapping.invalidate_lock#5); lock(&ni->ni_lock/4); *** DEADLOCK *** 3 locks held by syz-executor.5/6634: #0: ffff0001146d4460 (sb_writers#17){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2938 [inline] #0: ffff0001146d4460 (sb_writers#17){.+.+}-{0:0}, at: vfs_fallocate+0x2e4/0x388 fs/open.c:322 #1: ffff0001116f5d68 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline] #1: ffff0001116f5d68 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: ntfs_fallocate+0x1a4/0x904 fs/ntfs3/file.c:474 #2: ffff0001116f5f08 (mapping.invalidate_lock#5){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline] #2: ffff0001116f5f08 (mapping.invalidate_lock#5){++++}-{3:3}, at: ntfs_fallocate+0x218/0x904 fs/ntfs3/file.c:488 stack backtrace: CPU: 0 PID: 6634 Comm: syz-executor.5 Not tainted 6.2.0-rc7-syzkaller-17907-g2d3827b3f393 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023 Call trace: dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106 dump_stack+0x1c/0x28 lib/dump_stack.c:113 print_circular_bug+0x2c4/0x2c8 kernel/locking/lockdep.c:2055 check_noncircular+0x148/0x150 kernel/locking/lockdep.c:2177 check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain kernel/locking/lockdep.c:3831 [inline] __lock_acquire+0x1670/0x2f48 kernel/locking/lockdep.c:5055 lock_acquire+0x164/0x334 kernel/locking/lockdep.c:5668 __mutex_lock_common+0xd4/0xf64 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 ni_lock fs/ntfs3/ntfs_fs.h:1122 [inline] ntfs_fallocate+0x5d0/0x904 fs/ntfs3/file.c:568 vfs_fallocate+0x328/0x388 fs/open.c:323 ksys_fallocate fs/open.c:346 [inline] __do_sys_fallocate fs/open.c:354 [inline] __se_sys_fallocate fs/open.c:352 [inline] __arm64_sys_fallocate+0x5c/0xac fs/open.c:352 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x64/0x178 arch/arm64/kernel/syscall.c:52 el0_svc_common+0xbc/0x180 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x110 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x14c arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591 ntfs3: loop5: ino=21, "cgroup.controllers" attr_insert_range