loop0: detected capacity change from 0 to 4096 ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/4398 is trying to acquire lock: ffff0000d7802398 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0xa0/0x128 mm/memory.c:5356 but task is already holding lock: ffff0000e2147240 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: inode_trylock include/linux/fs.h:807 [inline] ffff0000e2147240 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: ntfs_file_write_iter+0x18c/0x49c fs/ntfs3/file.c:1123 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}: down_write+0xbc/0x12c kernel/locking/rwsem.c:1551 inode_lock include/linux/fs.h:787 [inline] ntfs_file_mmap+0x410/0x584 fs/ntfs3/file.c:401 call_mmap include/linux/fs.h:2177 [inline] mmap_file+0x6c/0xc8 mm/util.c:1092 __mmap_region mm/mmap.c:1792 [inline] mmap_region+0xadc/0x1390 mm/mmap.c:2929 do_mmap+0x67c/0xdb4 mm/mmap.c:1582 vm_mmap_pgoff+0x184/0x284 mm/util.c:551 ksys_mmap_pgoff+0x410/0x620 mm/mmap.c:1631 __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/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 -> #0 (&mm->mmap_lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2928/0x651c kernel/locking/lockdep.c:5012 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623 __might_fault+0xc8/0x128 mm/memory.c:5357 fault_in_readable+0x1ac/0x354 mm/gup.c:1801 fault_in_iov_iter_readable+0x120/0x248 lib/iov_iter.c:460 generic_perform_write+0x14c/0x480 mm/filemap.c:3775 __generic_file_write_iter+0x23c/0x454 mm/filemap.c:3912 ntfs_file_write_iter+0x408/0x49c fs/ntfs3/file.c:1144 call_write_iter include/linux/fs.h:2172 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x7c8/0xa2c fs/read_write.c:594 ksys_write+0x120/0x210 fs/read_write.c:647 __do_sys_write fs/read_write.c:659 [inline] __se_sys_write fs/read_write.c:656 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:656 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#20); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#20); lock(&mm->mmap_lock); *** DEADLOCK *** 3 locks held by syz-executor.0/4398: #0: ffff0000da9acff0 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x118/0x170 fs/file.c:1058 #1: ffff0000c99d0460 (sb_writers#12){.+.+}-{0:0}, at: vfs_write+0x228/0xa2c fs/read_write.c:590 #2: ffff0000e2147240 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: inode_trylock include/linux/fs.h:807 [inline] #2: ffff0000e2147240 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: ntfs_file_write_iter+0x18c/0x49c fs/ntfs3/file.c:1123 stack backtrace: CPU: 0 PID: 4398 Comm: syz-executor.0 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025 Call trace: dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216 __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:2011 check_noncircular+0x240/0x2d4 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2928/0x651c kernel/locking/lockdep.c:5012 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623 __might_fault+0xc8/0x128 mm/memory.c:5357 fault_in_readable+0x1ac/0x354 mm/gup.c:1801 fault_in_iov_iter_readable+0x120/0x248 lib/iov_iter.c:460 generic_perform_write+0x14c/0x480 mm/filemap.c:3775 __generic_file_write_iter+0x23c/0x454 mm/filemap.c:3912 ntfs_file_write_iter+0x408/0x49c fs/ntfs3/file.c:1144 call_write_iter include/linux/fs.h:2172 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x7c8/0xa2c fs/read_write.c:594 ksys_write+0x120/0x210 fs/read_write.c:647 __do_sys_write fs/read_write.c:659 [inline] __se_sys_write fs/read_write.c:656 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:656 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP Modules linked in: CPU: 0 PID: 4398 Comm: syz-executor.0 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025 pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc) pc : fault_in_readable+0x26c/0x354 mm/gup.c:1801 lr : fault_in_readable+0x248/0x354 mm/gup.c:1801 sp : ffff80001f6377b0 x29: ffff80001f6377d0 x28: 0000000000000000 x27: 0000000000001000 x26: 0000000000000000 x25: 0000000000000000 x24: 00000000fffffff2 x23: 1fffe0001b12ca38 x22: ffff0000d89651c0 x21: 0000000000000000 x20: 0000000000000000 x19: dfff800000000000 x18: 0000000000000001 x17: 0000000000000000 x16: ffff800008733cd0 x15: 00000000ffffffff x14: 0000000000ff0100 x13: 0000000000000001 x12: 0000000000ff0100 x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000 x8 : 0000000000000000 x7 : 0000000000000001 x6 : 0000000000000001 x5 : ffff80001f636a18 x4 : ffff80001424f3e0 x3 : ffff8000082fc310 x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000 Call trace: fault_in_readable+0x26c/0x354 mm/gup.c:1801 fault_in_iov_iter_readable+0x120/0x248 lib/iov_iter.c:460 generic_perform_write+0x14c/0x480 mm/filemap.c:3775 __generic_file_write_iter+0x23c/0x454 mm/filemap.c:3912 ntfs_file_write_iter+0x408/0x49c fs/ntfs3/file.c:1144 call_write_iter include/linux/fs.h:2172 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x7c8/0xa2c fs/read_write.c:594 ksys_write+0x120/0x210 fs/read_write.c:647 __do_sys_write fs/read_write.c:659 [inline] __se_sys_write fs/read_write.c:656 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:656 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 Code: 381f43b5 2a1503f8 2a1503e0 38400909 (381f43a9) ---[ end trace f7efec7dfb6ffcf2 ]--- ---------------- Code disassembly (best guess): 0: 381f43b5 sturb w21, [x29, #-12] 4: 2a1503f8 mov w24, w21 8: 2a1503e0 mov w0, w21 c: 38400909 ldtrb w9, [x8] * 10: 381f43a9 sturb w9, [x29, #-12] <-- trapping instruction