ntfs3: Cannot use different iocharset when remounting! ====================================================== WARNING: possible circular locking dependency detected 6.14.0-syzkaller-01103-g2df0c02dab82 #0 Not tainted ------------------------------------------------------ syz.5.1109/16282 is trying to acquire lock: ffff888055457918 (&sb->s_type->i_mutex_key#21){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline] ffff888055457918 (&sb->s_type->i_mutex_key#21){+.+.}-{4:4}, at: ntfs_file_mmap+0x63a/0x880 fs/ntfs3/file.c:379 but task is already holding lock: ffff8880559b6360 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:152 [inline] ffff8880559b6360 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x214/0x530 mm/util.c:576 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&mm->mmap_lock){++++}-{4:4}: lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866 gup_fast_fallback+0x261/0x29d0 mm/gup.c:3406 pin_user_pages_fast+0xd2/0x160 mm/gup.c:3530 iov_iter_extract_user_pages lib/iov_iter.c:1849 [inline] iov_iter_extract_pages+0x3bd/0x5c0 lib/iov_iter.c:1912 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+0x145f/0x48d0 fs/direct-io.c:1243 blockdev_direct_IO include/linux/fs.h:3414 [inline] ntfs_direct_IO+0x194/0x370 fs/ntfs3/inode.c:809 generic_file_direct_write+0x1e8/0x400 mm/filemap.c:4036 __generic_file_write_iter+0x126/0x230 mm/filemap.c:4205 ntfs_file_write_iter+0x6ee/0x7f0 fs/ntfs3/file.c:1267 do_iter_readv_writev+0x71f/0x9d0 vfs_writev+0x38d/0xbc0 fs/read_write.c:1055 do_writev+0x1b8/0x360 fs/read_write.c:1101 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&sb->s_type->i_mutex_key#21){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xa69/0x24e0 kernel/locking/lockdep.c:3909 __lock_acquire+0xad5/0xd80 kernel/locking/lockdep.c:5235 lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866 down_write+0x9c/0x220 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:867 [inline] ntfs_file_mmap+0x63a/0x880 fs/ntfs3/file.c:379 call_mmap include/linux/fs.h:2235 [inline] mmap_file mm/internal.h:124 [inline] __mmap_new_file_vma mm/vma.c:2296 [inline] __mmap_new_vma mm/vma.c:2360 [inline] __mmap_region mm/vma.c:2462 [inline] mmap_region+0x2479/0x2fc0 mm/vma.c:2540 do_mmap+0xd42/0x1420 mm/mmap.c:561 vm_mmap_pgoff+0x2a2/0x530 mm/util.c:578 ksys_mmap_pgoff+0x4ee/0x720 mm/mmap.c:607 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f 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#21); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#21); *** DEADLOCK *** 1 lock held by syz.5.1109/16282: #0: ffff8880559b6360 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:152 [inline] #0: ffff8880559b6360 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x214/0x530 mm/util.c:576 stack backtrace: CPU: 1 UID: 0 PID: 16282 Comm: syz.5.1109 Not tainted 6.14.0-syzkaller-01103-g2df0c02dab82 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2079 check_noncircular+0x142/0x160 kernel/locking/lockdep.c:2211 check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xa69/0x24e0 kernel/locking/lockdep.c:3909 __lock_acquire+0xad5/0xd80 kernel/locking/lockdep.c:5235 lock_acquire+0x116/0x2f0 kernel/locking/lockdep.c:5866 down_write+0x9c/0x220 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:867 [inline] ntfs_file_mmap+0x63a/0x880 fs/ntfs3/file.c:379 call_mmap include/linux/fs.h:2235 [inline] mmap_file mm/internal.h:124 [inline] __mmap_new_file_vma mm/vma.c:2296 [inline] __mmap_new_vma mm/vma.c:2360 [inline] __mmap_region mm/vma.c:2462 [inline] mmap_region+0x2479/0x2fc0 mm/vma.c:2540 do_mmap+0xd42/0x1420 mm/mmap.c:561 vm_mmap_pgoff+0x2a2/0x530 mm/util.c:578 ksys_mmap_pgoff+0x4ee/0x720 mm/mmap.c:607 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f1e7e98d169 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f1e7f7fc038 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 RAX: ffffffffffffffda RBX: 00007f1e7eba5fa0 RCX: 00007f1e7e98d169 RDX: 0000000000000002 RSI: 0000000000001000 RDI: 0000200000001000 RBP: 00007f1e7ea0e2a0 R08: 0000000000000004 R09: 0000000000000000 R10: 0000000000000011 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f1e7eba5fa0 R15: 00007fffad5f8f08