====================================================== WARNING: possible circular locking dependency detected 6.1.121-syzkaller #0 Tainted: G W ------------------------------------------------------ syz.0.363/5338 is trying to acquire lock: ffff0000d9c53748 (&mm->mmap_lock){++++}-{3:3}, at: get_current arch/arm64/include/asm/current.h:19 [inline] ffff0000d9c53748 (&mm->mmap_lock){++++}-{3:3}, at: internal_get_user_pages_fast+0x17c/0x2424 mm/gup.c:3031 but task is already holding lock: ffff0000f3da6ae0 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: inode_trylock include/linux/fs.h:778 [inline] ffff0000f3da6ae0 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: ntfs_file_write_iter+0x190/0x580 fs/ntfs3/file.c:1144 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}: down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ntfs_file_mmap+0x4b0/0x688 fs/ntfs3/file.c:399 call_mmap include/linux/fs.h:2270 [inline] mmap_file+0x6c/0xc8 mm/util.c:1109 __mmap_region mm/mmap.c:2760 [inline] mmap_region+0x128c/0x2208 mm/mmap.c:2904 do_mmap+0x9ac/0x110c mm/mmap.c:1424 vm_mmap_pgoff+0x1a4/0x2b4 mm/util.c:520 ksys_mmap_pgoff+0x3c8/0x5b0 mm/mmap.c:1470 __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:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #0 (&mm->mmap_lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x3338/0x7680 kernel/locking/lockdep.c:5049 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5662 internal_get_user_pages_fast+0x1c0/0x2424 mm/gup.c:3031 get_user_pages_fast+0x60/0x94 mm/gup.c:3139 __iov_iter_get_pages_alloc+0x320/0x928 lib/iov_iter.c:1460 iov_iter_get_pages2+0xd4/0x130 lib/iov_iter.c:1503 dio_refill_pages fs/direct-io.c:172 [inline] dio_get_page fs/direct-io.c:215 [inline] do_direct_IO fs/direct-io.c:932 [inline] __blockdev_direct_IO+0xe78/0x3ef4 fs/direct-io.c:1266 blockdev_direct_IO include/linux/fs.h:3342 [inline] ntfs_direct_IO+0x174/0x304 fs/ntfs3/inode.c:800 generic_file_direct_write+0x234/0x538 mm/filemap.c:3769 __generic_file_write_iter+0x1bc/0x388 mm/filemap.c:3929 ntfs_file_write_iter+0x4d4/0x580 fs/ntfs3/file.c:1165 call_write_iter include/linux/fs.h:2265 [inline] aio_write+0x588/0x824 fs/aio.c:1615 io_submit_one+0x824/0x15b8 fs/aio.c:2034 __do_sys_io_submit fs/aio.c:2093 [inline] __se_sys_io_submit fs/aio.c:2063 [inline] __arm64_sys_io_submit+0x248/0x3c8 fs/aio.c:2063 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#20); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#20); lock(&mm->mmap_lock); *** DEADLOCK *** 1 lock held by syz.0.363/5338: #0: ffff0000f3da6ae0 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: inode_trylock include/linux/fs.h:778 [inline] #0: ffff0000f3da6ae0 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: ntfs_file_write_iter+0x190/0x580 fs/ntfs3/file.c:1144 stack backtrace: CPU: 0 PID: 5338 Comm: syz.0.363 Tainted: G W 6.1.121-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 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+0x108/0x170 lib/dump_stack.c:106 dump_stack+0x1c/0x58 lib/dump_stack.c:113 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2048 check_noncircular+0x2cc/0x378 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x3338/0x7680 kernel/locking/lockdep.c:5049 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5662 internal_get_user_pages_fast+0x1c0/0x2424 mm/gup.c:3031 get_user_pages_fast+0x60/0x94 mm/gup.c:3139 __iov_iter_get_pages_alloc+0x320/0x928 lib/iov_iter.c:1460 iov_iter_get_pages2+0xd4/0x130 lib/iov_iter.c:1503 dio_refill_pages fs/direct-io.c:172 [inline] dio_get_page fs/direct-io.c:215 [inline] do_direct_IO fs/direct-io.c:932 [inline] __blockdev_direct_IO+0xe78/0x3ef4 fs/direct-io.c:1266 blockdev_direct_IO include/linux/fs.h:3342 [inline] ntfs_direct_IO+0x174/0x304 fs/ntfs3/inode.c:800 generic_file_direct_write+0x234/0x538 mm/filemap.c:3769 __generic_file_write_iter+0x1bc/0x388 mm/filemap.c:3929 ntfs_file_write_iter+0x4d4/0x580 fs/ntfs3/file.c:1165 call_write_iter include/linux/fs.h:2265 [inline] aio_write+0x588/0x824 fs/aio.c:1615 io_submit_one+0x824/0x15b8 fs/aio.c:2034 __do_sys_io_submit fs/aio.c:2093 [inline] __se_sys_io_submit fs/aio.c:2063 [inline] __arm64_sys_io_submit+0x248/0x3c8 fs/aio.c:2063 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585