====================================================== WARNING: possible circular locking dependency detected 6.13.0-rc2-syzkaller-g2e7aff49b5da #0 Not tainted ------------------------------------------------------ syz.0.298/8574 is trying to acquire lock: ffff0000cba00a10 (&mm->mmap_lock){++++}-{4:4}, at: get_current arch/arm64/include/asm/current.h:19 [inline] ffff0000cba00a10 (&mm->mmap_lock){++++}-{4:4}, at: gup_fast_fallback+0x1b8/0x3150 mm/gup.c:3416 but task is already holding lock: ffff0000dc9a8af0 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline] ffff0000dc9a8af0 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}, at: __blockdev_direct_IO+0x274/0x3648 fs/direct-io.c:1140 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}: down_write+0x50/0xc0 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:818 [inline] ntfs_file_mmap+0x48c/0x6b8 fs/ntfs3/file.c:379 call_mmap include/linux/fs.h:2183 [inline] mmap_file mm/internal.h:124 [inline] __mmap_new_file_vma mm/vma.c:2291 [inline] __mmap_new_vma mm/vma.c:2355 [inline] __mmap_region+0x1854/0x2180 mm/vma.c:2456 mmap_region+0x1cc/0x370 mm/mmap.c:1348 do_mmap+0x8b0/0xfd0 mm/mmap.c:496 vm_mmap_pgoff+0x1a0/0x38c mm/util.c:580 ksys_mmap_pgoff+0x3a4/0x5c8 mm/mmap.c:542 __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:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 -> #0 (&mm->mmap_lock){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x34f0/0x7904 kernel/locking/lockdep.c:5226 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5849 gup_fast_fallback+0x204/0x3150 mm/gup.c:3416 pin_user_pages_fast+0xa4/0x100 mm/gup.c:3540 iov_iter_extract_user_pages lib/iov_iter.c:1844 [inline] iov_iter_extract_pages+0x348/0x678 lib/iov_iter.c:1907 dio_refill_pages fs/direct-io.c:172 [inline] dio_get_page fs/direct-io.c:213 [inline] do_direct_IO fs/direct-io.c:915 [inline] __blockdev_direct_IO+0xdf0/0x3648 fs/direct-io.c:1243 blockdev_direct_IO include/linux/fs.h:3313 [inline] ntfs_direct_IO+0x170/0x300 fs/ntfs3/inode.c:806 generic_file_read_iter+0x2b0/0x450 mm/filemap.c:2811 ntfs_file_read_iter+0x200/0x264 fs/ntfs3/file.c:908 new_sync_read fs/read_write.c:484 [inline] vfs_read+0x740/0x970 fs/read_write.c:565 ksys_read+0x15c/0x26c fs/read_write.c:708 __do_sys_read fs/read_write.c:717 [inline] __se_sys_read fs/read_write.c:715 [inline] __arm64_sys_read+0x7c/0x90 fs/read_write.c:715 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#25); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#25); rlock(&mm->mmap_lock); *** DEADLOCK *** 2 locks held by syz.0.298/8574: #0: ffff0000d906feb8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x220/0x2ac fs/file.c:1191 #1: ffff0000dc9a8af0 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline] #1: ffff0000dc9a8af0 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}, at: __blockdev_direct_IO+0x274/0x3648 fs/direct-io.c:1140 stack backtrace: CPU: 1 UID: 0 PID: 8574 Comm: syz.0.298 Not tainted 6.13.0-rc2-syzkaller-g2e7aff49b5da #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:484 (C) __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 print_circular_bug+0x154/0x1c0 kernel/locking/lockdep.c:2074 check_noncircular+0x310/0x404 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x34f0/0x7904 kernel/locking/lockdep.c:5226 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5849 gup_fast_fallback+0x204/0x3150 mm/gup.c:3416 pin_user_pages_fast+0xa4/0x100 mm/gup.c:3540 iov_iter_extract_user_pages lib/iov_iter.c:1844 [inline] iov_iter_extract_pages+0x348/0x678 lib/iov_iter.c:1907 dio_refill_pages fs/direct-io.c:172 [inline] dio_get_page fs/direct-io.c:213 [inline] do_direct_IO fs/direct-io.c:915 [inline] __blockdev_direct_IO+0xdf0/0x3648 fs/direct-io.c:1243 blockdev_direct_IO include/linux/fs.h:3313 [inline] ntfs_direct_IO+0x170/0x300 fs/ntfs3/inode.c:806 generic_file_read_iter+0x2b0/0x450 mm/filemap.c:2811 ntfs_file_read_iter+0x200/0x264 fs/ntfs3/file.c:908 new_sync_read fs/read_write.c:484 [inline] vfs_read+0x740/0x970 fs/read_write.c:565 ksys_read+0x15c/0x26c fs/read_write.c:708 __do_sys_read fs/read_write.c:717 [inline] __se_sys_read fs/read_write.c:715 [inline] __arm64_sys_read+0x7c/0x90 fs/read_write.c:715 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600