Warning: Permanently added '10.128.1.117' (ED25519) to the list of known hosts.
executing program
[   40.585100][ T4015] loop0: detected capacity change from 0 to 4096
[   40.707322][ T4015] ntfs3: loop0: Different NTFS' sector size (4096) and media sector size (512)
[   40.722009][ T4015] ntfs3: loop0: Mark volume as dirty due to NTFS errors
[   40.734772][ T4015] 
[   40.735437][ T4015] ======================================================
[   40.737395][ T4015] WARNING: possible circular locking dependency detected
[   40.739386][ T4015] 5.15.165-syzkaller #0 Not tainted
[   40.740859][ T4015] ------------------------------------------------------
[   40.742864][ T4015] syz-executor116/4015 is trying to acquire lock:
[   40.744777][ T4015] ffff0000def8f240 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: ntfs_file_mmap+0x4b0/0x688
[   40.747731][ T4015] 
[   40.747731][ T4015] but task is already holding lock:
[   40.749734][ T4015] ffff0000c7fa1818 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15c/0x2b4
[   40.752201][ T4015] 
[   40.752201][ T4015] which lock already depends on the new lock.
[   40.752201][ T4015] 
[   40.755140][ T4015] 
[   40.755140][ T4015] the existing dependency chain (in reverse order) is:
[   40.757583][ T4015] 
[   40.757583][ T4015] -> #1 (&mm->mmap_lock){++++}-{3:3}:
[   40.759540][ T4015]        __might_fault+0xc8/0x128
[   40.760974][ T4015]        fault_in_readable+0xdc/0x56c
[   40.762417][ T4015]        fault_in_iov_iter_readable+0x130/0x1b0
[   40.764159][ T4015]        generic_perform_write+0x198/0x520
[   40.765688][ T4015]        __generic_file_write_iter+0x230/0x454
[   40.767404][ T4015]        ntfs_file_write_iter+0x40c/0x49c
[   40.769054][ T4015]        vfs_write+0x884/0xb44
[   40.770359][ T4015]        ksys_write+0x15c/0x26c
[   40.771772][ T4015]        __arm64_sys_write+0x7c/0x90
[   40.773220][ T4015]        invoke_syscall+0x98/0x2b8
[   40.774626][ T4015]        el0_svc_common+0x138/0x258
[   40.776057][ T4015]        do_el0_svc+0x58/0x14c
[   40.777362][ T4015]        el0_svc+0x7c/0x1f0
[   40.778629][ T4015]        el0t_64_sync_handler+0x84/0xe4
[   40.780207][ T4015]        el0t_64_sync+0x1a0/0x1a4
[   40.781593][ T4015] 
[   40.781593][ T4015] -> #0 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}:
[   40.784096][ T4015]        __lock_acquire+0x32d4/0x7638
[   40.785563][ T4015]        lock_acquire+0x240/0x77c
[   40.786970][ T4015]        down_write+0xbc/0x12c
[   40.788196][ T4015]        ntfs_file_mmap+0x4b0/0x688
[   40.789535][ T4015]        mmap_region+0xcb4/0x12f0
[   40.790938][ T4015]        do_mmap+0x6c0/0xcec
[   40.792176][ T4015]        vm_mmap_pgoff+0x1a4/0x2b4
[   40.793757][ T4015]        ksys_mmap_pgoff+0x458/0x668
[   40.795511][ T4015]        __arm64_sys_mmap+0xf8/0x110
[   40.797031][ T4015]        invoke_syscall+0x98/0x2b8
[   40.798454][ T4015]        el0_svc_common+0x138/0x258
[   40.799938][ T4015]        do_el0_svc+0x58/0x14c
[   40.801239][ T4015]        el0_svc+0x7c/0x1f0
[   40.802438][ T4015]        el0t_64_sync_handler+0x84/0xe4
[   40.804016][ T4015]        el0t_64_sync+0x1a0/0x1a4
[   40.805443][ T4015] 
[   40.805443][ T4015] other info that might help us debug this:
[   40.805443][ T4015] 
[   40.808321][ T4015]  Possible unsafe locking scenario:
[   40.808321][ T4015] 
[   40.810401][ T4015]        CPU0                    CPU1
[   40.811910][ T4015]        ----                    ----
[   40.813376][ T4015]   lock(&mm->mmap_lock);
[   40.814559][ T4015]                                lock(&sb->s_type->i_mutex_key#17);
[   40.816754][ T4015]                                lock(&mm->mmap_lock);
[   40.818613][ T4015]   lock(&sb->s_type->i_mutex_key#17);
[   40.820121][ T4015] 
[   40.820121][ T4015]  *** DEADLOCK ***
[   40.820121][ T4015] 
[   40.822301][ T4015] 1 lock held by syz-executor116/4015:
[   40.823814][ T4015]  #0: ffff0000c7fa1818 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15c/0x2b4
[   40.826403][ T4015] 
[   40.826403][ T4015] stack backtrace:
[   40.828046][ T4015] CPU: 0 PID: 4015 Comm: syz-executor116 Not tainted 5.15.165-syzkaller #0
[   40.830458][ T4015] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
[   40.833229][ T4015] Call trace:
[   40.834153][ T4015]  dump_backtrace+0x0/0x530
[   40.835367][ T4015]  show_stack+0x2c/0x3c
[   40.836484][ T4015]  dump_stack_lvl+0x108/0x170
[   40.837723][ T4015]  dump_stack+0x1c/0x58
[   40.838898][ T4015]  print_circular_bug+0x150/0x1b8
[   40.840252][ T4015]  check_noncircular+0x2cc/0x378
[   40.841605][ T4015]  __lock_acquire+0x32d4/0x7638
[   40.842987][ T4015]  lock_acquire+0x240/0x77c
[   40.844270][ T4015]  down_write+0xbc/0x12c
[   40.845461][ T4015]  ntfs_file_mmap+0x4b0/0x688
[   40.846719][ T4015]  mmap_region+0xcb4/0x12f0
[   40.847906][ T4015]  do_mmap+0x6c0/0xcec
[   40.849017][ T4015]  vm_mmap_pgoff+0x1a4/0x2b4
[   40.850253][ T4015]  ksys_mmap_pgoff+0x458/0x668
[   40.851548][ T4015]  __arm64_sys_mmap+0xf8/0x110
[   40.852863][ T4015]  invoke_syscall+0x98/0x2b8
[   40.854068][ T4015]  el0_svc_common+0x138/0x258
[   40.855378][ T4015]  do_el0_svc+0x58/0x14c
[   40.856562][ T4015]  el0_svc+0x7c/0x1f0
[   40.857659][ T4015]  el0t_64_sync_handler+0x84/0xe4
[   40.859046][ T4015]  el0t_64_sync+0x1a0/0x1a4