loop2: detected capacity change from 0 to 4096 ====================================================== WARNING: possible circular locking dependency detected 6.10.0-rc7-syzkaller-gc912bf709078 #0 Not tainted ------------------------------------------------------ syz.2.469/9140 is trying to acquire lock: ffff0000e03ea5e0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1123 [inline] ffff0000e03ea5e0 (&ni->ni_lock/4){+.+.}-{3:3}, at: attr_data_get_block+0x34c/0x23ac fs/ntfs3/attrib.c:914 but task is already holding lock: ffff0000ccb55988 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:122 [inline] ffff0000ccb55988 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x154/0x38c mm/util.c:571 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&mm->mmap_lock){++++}-{3:3}: __might_fault+0xc4/0x124 mm/memory.c:6234 _copy_to_user include/linux/uaccess.h:165 [inline] copy_to_user include/linux/uaccess.h:191 [inline] fiemap_fill_next_extent+0x1b0/0x390 fs/ioctl.c:145 ni_fiemap+0x7dc/0xe10 fs/ntfs3/frecord.c:2065 ntfs_fiemap+0x110/0x168 fs/ntfs3/file.c:1215 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x172c/0x2404 fs/ioctl.c:841 __do_sys_ioctl fs/ioctl.c:905 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __arm64_sys_ioctl+0xe4/0x1c8 fs/ioctl.c:893 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:131 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:150 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 -> #1 (&ni->file.run_lock){++++}-{3:3}: down_write+0x50/0xc0 kernel/locking/rwsem.c:1579 ntfs_set_size+0x130/0x200 fs/ntfs3/inode.c:849 ntfs_extend+0x130/0x3dc fs/ntfs3/file.c:335 ntfs_file_write_iter+0x338/0x628 fs/ntfs3/file.c:1124 new_sync_write fs/read_write.c:497 [inline] vfs_write+0x8f8/0xc38 fs/read_write.c:590 ksys_write+0x15c/0x26c fs/read_write.c:643 __do_sys_write fs/read_write.c:655 [inline] __se_sys_write fs/read_write.c:652 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:652 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:131 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:150 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 -> #0 (&ni->ni_lock/4){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x3384/0x763c kernel/locking/lockdep.c:5137 lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5754 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:608 __mutex_lock kernel/locking/mutex.c:752 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:804 ni_lock fs/ntfs3/ntfs_fs.h:1123 [inline] attr_data_get_block+0x34c/0x23ac fs/ntfs3/attrib.c:914 ntfs_file_mmap+0x3f0/0x6f0 fs/ntfs3/file.c:294 call_mmap include/linux/fs.h:2107 [inline] mmap_region+0xbb8/0x17d8 mm/mmap.c:2886 do_mmap+0x788/0xd90 mm/mmap.c:1397 vm_mmap_pgoff+0x1a0/0x38c mm/util.c:573 ksys_mmap_pgoff+0x3a4/0x5c8 mm/mmap.c:1443 __do_sys_mmap arch/arm64/kernel/sys.c:28 [inline] __se_sys_mmap arch/arm64/kernel/sys.c:21 [inline] __arm64_sys_mmap+0xf8/0x110 arch/arm64/kernel/sys.c:21 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:131 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:150 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 other info that might help us debug this: Chain exists of: &ni->ni_lock/4 --> &ni->file.run_lock --> &mm->mmap_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&mm->mmap_lock); lock(&ni->file.run_lock); lock(&mm->mmap_lock); lock(&ni->ni_lock/4); *** DEADLOCK *** 1 lock held by syz.2.469/9140: #0: ffff0000ccb55988 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:122 [inline] #0: ffff0000ccb55988 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x154/0x38c mm/util.c:571 stack backtrace: CPU: 0 PID: 9140 Comm: syz.2.469 Not tainted 6.10.0-rc7-syzkaller-gc912bf709078 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:317 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:324 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:114 dump_stack+0x1c/0x28 lib/dump_stack.c:123 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2060 check_noncircular+0x310/0x404 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x3384/0x763c kernel/locking/lockdep.c:5137 lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5754 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:608 __mutex_lock kernel/locking/mutex.c:752 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:804 ni_lock fs/ntfs3/ntfs_fs.h:1123 [inline] attr_data_get_block+0x34c/0x23ac fs/ntfs3/attrib.c:914 ntfs_file_mmap+0x3f0/0x6f0 fs/ntfs3/file.c:294 call_mmap include/linux/fs.h:2107 [inline] mmap_region+0xbb8/0x17d8 mm/mmap.c:2886 do_mmap+0x788/0xd90 mm/mmap.c:1397 vm_mmap_pgoff+0x1a0/0x38c mm/util.c:573 ksys_mmap_pgoff+0x3a4/0x5c8 mm/mmap.c:1443 __do_sys_mmap arch/arm64/kernel/sys.c:28 [inline] __se_sys_mmap arch/arm64/kernel/sys.c:21 [inline] __arm64_sys_mmap+0xf8/0x110 arch/arm64/kernel/sys.c:21 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:131 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:150 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598