====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Tainted: G L ------------------------------------------------------ syz.3.542/7998 is trying to acquire lock: ffff888036f6cfb8 (&mm->mmap_lock){++++}-{4:4}, at: __might_fault+0xaf/0x130 mm/memory.c:7271 but task is already holding lock: ffff888073acbe70 (&ctx->map_changing_lock){++++}-{4:4}, at: mfill_get_vma+0x162/0x660 mm/userfaultfd.c:226 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ctx->map_changing_lock){++++}-{4:4} : down_write+0x96/0x200 kernel/locking/rwsem.c:1625 userfaultfd_unmap_prep+0x24b/0x3e0 fs/userfaultfd.c:848 vms_gather_munmap_vmas+0x9c6/0x1370 mm/vma.c:1466 __mmap_setup mm/vma.c:2411 [inline] __mmap_region mm/vma.c:2739 [inline] mmap_region+0x85b/0x2240 mm/vma.c:2835 do_mmap+0xc39/0x10c0 mm/mmap.c:559 vm_mmap_pgoff+0x2c9/0x4f0 mm/util.c:581 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&mm->mmap_lock ){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868 __might_fault+0xcb/0x130 mm/memory.c:7271 userfaultfd_copy fs/userfaultfd.c:1648 [inline] userfaultfd_ioctl+0x2c01/0x4c70 fs/userfaultfd.c:2059 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/0xf80 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 ---- ---- rlock( &ctx->map_changing_lock); lock(&mm->mmap_lock); lock(&ctx->map_changing_lock); rlock(&mm->mmap_lock); *** DEADLOCK *** 2 locks held by syz.3.542/7998: #0: ffff888077bb3948 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x1d1/0x500 mm/mmap_lock.c:310 #1: ffff888073acbe70 (&ctx->map_changing_lock){++++}-{4:4}, at: mfill_get_vma+0x162/0x660 mm/userfaultfd.c:226 stack backtrace: CPU: 0 UID: 0 PID: 7998 Comm: syz.3.542 Tainted: G L syzkaller #0 PREEMPT(full) Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043 check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2175 check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868 __might_fault+0xcb/0x130 mm/memory.c:7271 userfaultfd_copy fs/userfaultfd.c:1648 [inline] userfaultfd_ioctl+0x2c01/0x4c70 fs/userfaultfd.c:2059 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fd9ab79c799 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fd9ac5d1028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fd9aba15fa0 RCX: 00007fd9ab79c799 RDX: 0000200000000000 RSI: 00000000c028aa03 RDI: 0000000000000003 RBP: 00007fd9ab832c99 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fd9aba16038 R14: 00007fd9aba15fa0 R15: 00007ffee9be2bb8