loop1: detected capacity change from 0 to 4096 ====================================================== WARNING: possible circular locking dependency detected 6.1.138-syzkaller #0 Not tainted ------------------------------------------------------ syz.1.223/5029 is trying to acquire lock: ffff0000f5324d60 (&sb->s_type->i_mutex_key#29){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] ffff0000f5324d60 (&sb->s_type->i_mutex_key#29){+.+.}-{3:3}, at: ntfs_file_mmap+0x3e8/0x55c fs/ntfs3/file.c:320 but task is already holding lock: ffff0000cd64ab48 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline] ffff0000cd64ab48 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x138/0x284 mm/util.c:518 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&mm->mmap_lock){++++}-{3:3}: internal_get_user_pages_fast+0x164/0x1a70 mm/gup.c:3042 get_user_pages_fast+0x60/0x94 mm/gup.c:3150 __iov_iter_get_pages_alloc+0x2e0/0x800 lib/iov_iter.c:1460 iov_iter_get_pages2+0x74/0xbc 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+0xc74/0x318c fs/direct-io.c:1266 blockdev_direct_IO include/linux/fs.h:3342 [inline] ntfs_direct_IO+0x174/0x324 fs/ntfs3/inode.c:798 generic_file_direct_write+0x31c/0x620 mm/filemap.c:3770 __generic_file_write_iter+0x1bc/0x37c mm/filemap.c:3930 ntfs_file_write_iter+0x4d4/0x584 fs/ntfs3/file.c:1081 call_write_iter include/linux/fs.h:2265 [inline] aio_write+0x54c/0x798 fs/aio.c:1615 __io_submit_one fs/aio.c:-1 [inline] io_submit_one+0x7a8/0x11cc 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+0x268/0x3e4 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/0x138 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 (&sb->s_type->i_mutex_key#29){+.+.}-{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+0x293c/0x6544 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ntfs_file_mmap+0x3e8/0x55c fs/ntfs3/file.c:320 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+0xcc8/0x1860 mm/mmap.c:2904 do_mmap+0x978/0x10dc mm/mmap.c:1424 vm_mmap_pgoff+0x184/0x284 mm/util.c:520 ksys_mmap_pgoff+0x3b8/0x5a0 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/0x138 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(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#29); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#29); *** DEADLOCK *** 1 lock held by syz.1.223/5029: #0: ffff0000cd64ab48 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline] #0: ffff0000cd64ab48 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x138/0x284 mm/util.c:518 stack backtrace: CPU: 0 PID: 5029 Comm: syz.1.223 Not tainted 6.1.138-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call trace: dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2048 check_noncircular+0x240/0x2d4 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+0x293c/0x6544 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ntfs_file_mmap+0x3e8/0x55c fs/ntfs3/file.c:320 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+0xcc8/0x1860 mm/mmap.c:2904 do_mmap+0x978/0x10dc mm/mmap.c:1424 vm_mmap_pgoff+0x184/0x284 mm/util.c:520 ksys_mmap_pgoff+0x3b8/0x5a0 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/0x138 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