Warning: Permanently added '10.128.1.4' (ED25519) to the list of known hosts.
executing program
syzkaller login: [   44.065864][ T4018] loop0: detected capacity change from 0 to 4096
[   44.261674][ T4018] 
[   44.262351][ T4018] ======================================================
[   44.264248][ T4018] WARNING: possible circular locking dependency detected
[   44.266153][ T4018] 5.15.179-syzkaller #0 Not tainted
[   44.267502][ T4018] ------------------------------------------------------
[   44.269392][ T4018] syz-executor271/4018 is trying to acquire lock:
[   44.271188][ T4018] ffff0000ddbdf240 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: ntfs_file_mmap+0x4b0/0x688
[   44.274035][ T4018] 
[   44.274035][ T4018] but task is already holding lock:
[   44.276105][ T4018] ffff0000c1f44bd8 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15c/0x2b4
[   44.278557][ T4018] 
[   44.278557][ T4018] which lock already depends on the new lock.
[   44.278557][ T4018] 
[   44.281509][ T4018] 
[   44.281509][ T4018] the existing dependency chain (in reverse order) is:
[   44.283967][ T4018] 
[   44.283967][ T4018] -> #1 (&mm->mmap_lock){++++}-{3:3}:
[   44.286080][ T4018]        __might_fault+0xc8/0x128
[   44.287460][ T4018]        fault_in_readable+0xdc/0x56c
[   44.288863][ T4018]        fault_in_iov_iter_readable+0x130/0x1b0
[   44.290565][ T4018]        generic_perform_write+0x198/0x520
[   44.292165][ T4018]        __generic_file_write_iter+0x230/0x454
[   44.293813][ T4018]        ntfs_file_write_iter+0x40c/0x49c
[   44.295375][ T4018]        vfs_write+0x884/0xb44
[   44.296606][ T4018]        ksys_write+0x15c/0x26c
[   44.297909][ T4018]        __arm64_sys_write+0x7c/0x90
[   44.299363][ T4018]        invoke_syscall+0x98/0x2b8
[   44.300753][ T4018]        el0_svc_common+0x138/0x258
[   44.302196][ T4018]        do_el0_svc+0x58/0x14c
[   44.303446][ T4018]        el0_svc+0x7c/0x1f0
[   44.304624][ T4018]        el0t_64_sync_handler+0x84/0xe4
[   44.306202][ T4018]        el0t_64_sync+0x1a0/0x1a4
[   44.307505][ T4018] 
[   44.307505][ T4018] -> #0 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}:
[   44.309885][ T4018]        __lock_acquire+0x32d4/0x7638
[   44.311323][ T4018]        lock_acquire+0x240/0x77c
[   44.312711][ T4018]        down_write+0xbc/0x12c
[   44.313990][ T4018]        ntfs_file_mmap+0x4b0/0x688
[   44.315449][ T4018]        mmap_file+0x6c/0xc8
[   44.316699][ T4018]        mmap_region+0xb24/0x1408
[   44.318050][ T4018]        do_mmap+0x698/0xdc4
[   44.319336][ T4018]        vm_mmap_pgoff+0x1a4/0x2b4
[   44.320743][ T4018]        ksys_mmap_pgoff+0x458/0x668
[   44.322155][ T4018]        __arm64_sys_mmap+0xf8/0x110
[   44.323567][ T4018]        invoke_syscall+0x98/0x2b8
[   44.324919][ T4018]        el0_svc_common+0x138/0x258
[   44.326322][ T4018]        do_el0_svc+0x58/0x14c
[   44.327631][ T4018]        el0_svc+0x7c/0x1f0
[   44.328762][ T4018]        el0t_64_sync_handler+0x84/0xe4
[   44.330319][ T4018]        el0t_64_sync+0x1a0/0x1a4
[   44.331687][ T4018] 
[   44.331687][ T4018] other info that might help us debug this:
[   44.331687][ T4018] 
[   44.334496][ T4018]  Possible unsafe locking scenario:
[   44.334496][ T4018] 
[   44.336587][ T4018]        CPU0                    CPU1
[   44.338043][ T4018]        ----                    ----
[   44.339504][ T4018]   lock(&mm->mmap_lock);
[   44.340690][ T4018]                                lock(&sb->s_type->i_mutex_key#17);
[   44.342847][ T4018]                                lock(&mm->mmap_lock);
[   44.344783][ T4018]   lock(&sb->s_type->i_mutex_key#17);
[   44.346301][ T4018] 
[   44.346301][ T4018]  *** DEADLOCK ***
[   44.346301][ T4018] 
[   44.348520][ T4018] 1 lock held by syz-executor271/4018:
[   44.350510][ T4018]  #0: ffff0000c1f44bd8 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15c/0x2b4
[   44.353095][ T4018] 
[   44.353095][ T4018] stack backtrace:
[   44.354736][ T4018] CPU: 0 PID: 4018 Comm: syz-executor271 Not tainted 5.15.179-syzkaller #0
[   44.357127][ T4018] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
[   44.359991][ T4018] Call trace:
[   44.360916][ T4018]  dump_backtrace+0x0/0x530
[   44.362252][ T4018]  show_stack+0x2c/0x3c
[   44.363431][ T4018]  dump_stack_lvl+0x108/0x170
[   44.364711][ T4018]  dump_stack+0x1c/0x58
[   44.365871][ T4018]  print_circular_bug+0x150/0x1b8
[   44.367318][ T4018]  check_noncircular+0x2cc/0x378
[   44.368696][ T4018]  __lock_acquire+0x32d4/0x7638
[   44.370040][ T4018]  lock_acquire+0x240/0x77c
[   44.371334][ T4018]  down_write+0xbc/0x12c
[   44.372506][ T4018]  ntfs_file_mmap+0x4b0/0x688
[   44.373784][ T4018]  mmap_file+0x6c/0xc8
[   44.374939][ T4018]  mmap_region+0xb24/0x1408
[   44.376184][ T4018]  do_mmap+0x698/0xdc4
[   44.377275][ T4018]  vm_mmap_pgoff+0x1a4/0x2b4
[   44.378516][ T4018]  ksys_mmap_pgoff+0x458/0x668
[   44.379825][ T4018]  __arm64_sys_mmap+0xf8/0x110
[   44.381145][ T4018]  invoke_syscall+0x98/0x2b8
[   44.382397][ T4018]  el0_svc_common+0x138/0x258
[   44.383716][ T4018]  do_el0_svc+0x58/0x14c
[   44.384823][ T4018]  el0_svc+0x7c/0x1f0
[   44.385898][ T4018]  el0t_64_sync_handler+0x84/0xe4
[   44.387270][ T4018]  el0t_64_sync+0x1a0/0x1a4
[   44.388888][ T4018] ntfs3: loop0: ino=21, "net_prio.prioidx" failed to extend initialized size to 208e24b.