Warning: Permanently added '10.128.1.24' (ED25519) to the list of known hosts. executing program [ 38.629075][ T4289] loop0: detected capacity change from 0 to 4096 [ 38.632400][ T4289] ======================================================= [ 38.632400][ T4289] WARNING: The mand mount option has been deprecated and [ 38.632400][ T4289] and is ignored by this kernel. Remove the mand [ 38.632400][ T4289] option from the mount to silence this warning. [ 38.632400][ T4289] ======================================================= [ 38.663994][ T4289] [ 38.664502][ T4289] ====================================================== [ 38.665882][ T4289] WARNING: possible circular locking dependency detected [ 38.667283][ T4289] 6.1.116-syzkaller #0 Not tainted [ 38.668403][ T4289] ------------------------------------------------------ [ 38.669801][ T4289] syz-executor352/4289 is trying to acquire lock: [ 38.671123][ T4289] ffff0000d4fb2548 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0x9c/0x124 [ 38.673109][ T4289] [ 38.673109][ T4289] but task is already holding lock: [ 38.674545][ T4289] ffff0000e5007240 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: ntfs_file_write_iter+0x190/0x580 [ 38.676762][ T4289] [ 38.676762][ T4289] which lock already depends on the new lock. [ 38.676762][ T4289] [ 38.678907][ T4289] [ 38.678907][ T4289] the existing dependency chain (in reverse order) is: [ 38.680835][ T4289] [ 38.680835][ T4289] -> #1 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}: [ 38.682593][ T4289] down_write+0x5c/0x88 [ 38.683603][ T4289] ntfs_file_mmap+0x4b0/0x688 [ 38.684742][ T4289] mmap_region+0xdd0/0x1a98 [ 38.685820][ T4289] do_mmap+0xa00/0x1108 [ 38.686774][ T4289] vm_mmap_pgoff+0x1a4/0x2b4 [ 38.687853][ T4289] ksys_mmap_pgoff+0x3c8/0x5b0 [ 38.689024][ T4289] __arm64_sys_mmap+0xf8/0x110 [ 38.690171][ T4289] invoke_syscall+0x98/0x2c0 [ 38.691243][ T4289] el0_svc_common+0x138/0x258 [ 38.692351][ T4289] do_el0_svc+0x64/0x218 [ 38.693346][ T4289] el0_svc+0x58/0x168 [ 38.694238][ T4289] el0t_64_sync_handler+0x84/0xf0 [ 38.695411][ T4289] el0t_64_sync+0x18c/0x190 [ 38.696517][ T4289] [ 38.696517][ T4289] -> #0 (&mm->mmap_lock){++++}-{3:3}: [ 38.698151][ T4289] __lock_acquire+0x3338/0x7680 [ 38.699266][ T4289] lock_acquire+0x26c/0x7cc [ 38.700348][ T4289] __might_fault+0xc4/0x124 [ 38.701368][ T4289] fault_in_readable+0x188/0x5f0 [ 38.702499][ T4289] fault_in_iov_iter_readable+0xcc/0x22c [ 38.703842][ T4289] generic_perform_write+0x1c8/0x55c [ 38.704973][ T4289] __generic_file_write_iter+0x168/0x388 [ 38.706251][ T4289] ntfs_file_write_iter+0x4d4/0x580 [ 38.707469][ T4289] vfs_write+0x610/0x91c [ 38.708574][ T4289] ksys_write+0x15c/0x26c [ 38.709599][ T4289] __arm64_sys_write+0x7c/0x90 [ 38.710667][ T4289] invoke_syscall+0x98/0x2c0 [ 38.711851][ T4289] el0_svc_common+0x138/0x258 [ 38.712976][ T4289] do_el0_svc+0x64/0x218 [ 38.713903][ T4289] el0_svc+0x58/0x168 [ 38.715015][ T4289] el0t_64_sync_handler+0x84/0xf0 [ 38.716173][ T4289] el0t_64_sync+0x18c/0x190 [ 38.717236][ T4289] [ 38.717236][ T4289] other info that might help us debug this: [ 38.717236][ T4289] [ 38.719332][ T4289] Possible unsafe locking scenario: [ 38.719332][ T4289] [ 38.720859][ T4289] CPU0 CPU1 [ 38.722017][ T4289] ---- ---- [ 38.723116][ T4289] lock(&sb->s_type->i_mutex_key#17); [ 38.724210][ T4289] lock(&mm->mmap_lock); [ 38.725666][ T4289] lock(&sb->s_type->i_mutex_key#17); [ 38.727393][ T4289] lock(&mm->mmap_lock); [ 38.728329][ T4289] [ 38.728329][ T4289] *** DEADLOCK *** [ 38.728329][ T4289] [ 38.730186][ T4289] 3 locks held by syz-executor352/4289: [ 38.731301][ T4289] #0: ffff0000d82cdc68 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x124/0x16c [ 38.733251][ T4289] #1: ffff0000da4e2460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x244/0x91c [ 38.735076][ T4289] #2: ffff0000e5007240 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: ntfs_file_write_iter+0x190/0x580 [ 38.737425][ T4289] [ 38.737425][ T4289] stack backtrace: [ 38.738653][ T4289] CPU: 1 PID: 4289 Comm: syz-executor352 Not tainted 6.1.116-syzkaller #0 [ 38.740386][ T4289] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 [ 38.742437][ T4289] Call trace: [ 38.743083][ T4289] dump_backtrace+0x1c8/0x1f4 [ 38.744076][ T4289] show_stack+0x2c/0x3c [ 38.744968][ T4289] dump_stack_lvl+0x108/0x170 [ 38.746055][ T4289] dump_stack+0x1c/0x58 [ 38.746889][ T4289] print_circular_bug+0x150/0x1b8 [ 38.747894][ T4289] check_noncircular+0x2cc/0x378 [ 38.748932][ T4289] __lock_acquire+0x3338/0x7680 [ 38.749851][ T4289] lock_acquire+0x26c/0x7cc [ 38.750789][ T4289] __might_fault+0xc4/0x124 [ 38.751658][ T4289] fault_in_readable+0x188/0x5f0 [ 38.752624][ T4289] fault_in_iov_iter_readable+0xcc/0x22c [ 38.753821][ T4289] generic_perform_write+0x1c8/0x55c [ 38.754908][ T4289] __generic_file_write_iter+0x168/0x388 [ 38.756012][ T4289] ntfs_file_write_iter+0x4d4/0x580 [ 38.757207][ T4289] vfs_write+0x610/0x91c [ 38.758056][ T4289] ksys_write+0x15c/0x26c [ 38.758924][ T4289] __arm64_sys_write+0x7c/0x90 [ 38.759962][ T4289] invoke_syscall+0x98/0x2c0 [ 38.760980][ T4289] el0_svc_common+0x138/0x258 [ 38.761977][ T4289] do_el0_svc+0x64/0x218 [ 38.762867][ T4289] el0_svc+0x58/0x168 [ 38.763695][ T4289] el0t_64_sync_handler+0x84/0xf0 [ 38.764738][ T4289] el0t_64_sync+0x18c/0x190