From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f79.google.com (mail-oo1-f79.google.com [209.85.161.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 991DC3FB06C for ; Fri, 24 Apr 2026 20:00:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.79 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777060837; cv=none; b=n00r+KcWXokDPHY+NbneP2+LXBEY9YXuIo4OiEL4X4kcc/fUZu9iCBxfDKZHPrxHnGP7fnb00I4iE/t/3S/WVxIN9WhEleIbtZVuk+rmljPqmOTk1GNNDnGAQgdOJM7jMUybyFANjg1Il/X2y/ZWV4PY25Q004IFiz/K26z8A1M= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777060837; c=relaxed/simple; bh=kJbDl8FCqqUHH7bbHJ4Yok28Di9tFbJ1g1fUukwBA5E=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=J4lBABkKyK69pO4+hsCUJYMI7WUbV31hyf0DhV/43CIva0fz8E3NRnWaBxYPADh8OhxWfN0c4aIYF70Ecxh8VJ4seI/U5jOLA8Ihbv4twGWYwpIbt1jr3nDDuKSI2kwoX0ro31XFIsYWG3Wqd0DetD9uuAaS9jWk/JtoBeyoa48= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.79 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f79.google.com with SMTP id 006d021491bc7-696233b2816so2671329eaf.1 for ; Fri, 24 Apr 2026 13:00:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777060834; x=1777665634; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ggGX+6weTYqFFNdLkFPYeANYaSekrOHoGD6NL8WI18o=; b=EWJ8wPmFMEYtWpjfIelYawFa4SxTmY95vpJqt1zllZ+jjx4WjBDf7tHfz8jOE8HER0 XaHNtnNmdw+ayj+ZKP7yMZV39eVZf+nIlqvts3Dg0QY/o/xQeGk9uL3giqdOlbYmWFcn OJEfyBz3qw4sB6mB80BCIjBQWOvCVgrafTCSdO3+omuvTRgJoaDiDEudXVR7FRin3Y8+ /2r85yqtf/UdsAQXVI7qDgI3sUMPFG68oVQ5Wd2uBCFViYvFqlg+JHnDmahaTbywnkNf 4RqErOoN7TfluLAHRmj03HY0U3yC12c4/psT/L3ehon3aS5pOeyUreG7oIwJo3Bl43W6 TOMQ== X-Forwarded-Encrypted: i=1; AFNElJ9xym8GwAkhZAIYIbb/0SjUGXBkaFqkCU9YHaUU3I+skqiMLlMf+LxozCRPWaaxk0lcESVP8XQzCyQHazk=@vger.kernel.org X-Gm-Message-State: AOJu0YxYWUfh5JHrILWVh2OhU6pdU1tah+35ZL6Mk3MNJ0yuuml5a26U 6vlgJxJb5+NEhUd2pAu2GIp0w9oZUJCfvBP/JT9FHvaGPjylYZONueDRz/sWPxMO3li7wWWqQpj muRKKpkacUKrLANeuSrt4skJaVjNeXeg5GUW7IsiBU3g360qLgnWXN1TzRI8= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:f024:b0:694:9d60:99ab with SMTP id 006d021491bc7-6949d60a6d0mr9785179eaf.6.1777060834437; Fri, 24 Apr 2026 13:00:34 -0700 (PDT) Date: Fri, 24 Apr 2026 13:00:34 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69ebcbe2.a00a0220.7773.0005.GAE@google.com> Subject: [syzbot] [mm?] WARNING: bad unlock balance in __zap_vma_range From: syzbot To: Liam.Howlett@oracle.com, akpm@linux-foundation.org, jannh@google.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org, pfalcato@suse.de, syzkaller-bugs@googlegroups.com, vbabka@kernel.org Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: c1f49dea2b8f Merge tag 'mm-hotfixes-stable-2026-04-19-00-1.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10b09f16580000 kernel config: https://syzkaller.appspot.com/x/.config?x=6a29a582d8ced859 dashboard link: https://syzkaller.appspot.com/bug?extid=d2be42d723da59b38697 compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-c1f49dea.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/402c79548d6e/vmlinux-c1f49dea.xz kernel image: https://storage.googleapis.com/syzbot-assets/1bc39526d7f4/bzImage-c1f49dea.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+d2be42d723da59b38697@syzkaller.appspotmail.com ===================================== WARNING: bad unlock balance detected! syzkaller #0 Not tainted ------------------------------------- dhcpcd-run-hook/5886 is trying to release lock (rcu_read_lock) at: [] rcu_lock_release include/linux/rcupdate.h:310 [inline] [] rcu_read_unlock include/linux/rcupdate.h:869 [inline] [] pte_unmap include/linux/pgtable.h:117 [inline] [] zap_pte_range mm/memory.c:1948 [inline] [] zap_pmd_range mm/memory.c:2004 [inline] [] zap_pud_range mm/memory.c:2032 [inline] [] zap_p4d_range mm/memory.c:2053 [inline] [] __zap_vma_range+0x22dc/0x4bf0 mm/memory.c:2093 but there are no more locks to release! other info that might help us debug this: 1 lock held by dhcpcd-run-hook/5886: #0: ffff88802b94b438 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_lock include/linux/mmap_lock.h:592 [inline] #0: ffff88802b94b438 (&mm->mmap_lock){++++}-{4:4}, at: exit_mmap+0x124/0xa10 mm/mmap.c:1284 stack backtrace: CPU: 2 UID: 0 PID: 5886 Comm: dhcpcd-run-hook Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120 print_unlock_imbalance_bug.part.0+0xfb/0x106 kernel/locking/lockdep.c:5298 print_unlock_imbalance_bug kernel/locking/lockdep.c:5278 [inline] __lock_release kernel/locking/lockdep.c:5537 [inline] lock_release kernel/locking/lockdep.c:5889 [inline] lock_release+0x28d/0x310 kernel/locking/lockdep.c:5875 rcu_lock_release include/linux/rcupdate.h:310 [inline] rcu_read_unlock include/linux/rcupdate.h:869 [inline] pte_unmap include/linux/pgtable.h:117 [inline] zap_pte_range mm/memory.c:1948 [inline] zap_pmd_range mm/memory.c:2004 [inline] zap_pud_range mm/memory.c:2032 [inline] zap_p4d_range mm/memory.c:2053 [inline] __zap_vma_range+0x22e1/0x4bf0 mm/memory.c:2093 unmap_vmas+0x299/0x5f0 mm/memory.c:2162 exit_mmap+0x1ef/0xa10 mm/mmap.c:1300 __mmput+0x12a/0x410 kernel/fork.c:1178 mmput+0x67/0x80 kernel/fork.c:1201 exit_mm kernel/exit.c:581 [inline] do_exit+0x833/0x2a60 kernel/exit.c:963 do_group_exit+0xd5/0x2a0 kernel/exit.c:1117 __do_sys_exit_group kernel/exit.c:1128 [inline] __se_sys_exit_group kernel/exit.c:1126 [inline] __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1126 x64_sys_call+0x102c/0x1530 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x10b/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f4a27bab6c5 Code: Unable to access opcode bytes at 0x7f4a27bab69b. RSP: 002b:00007ffe0faf6ed8 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007ffe0faf7104 RCX: 00007f4a27bab6c5 RDX: 00000000000000e7 RSI: ffffffffffffff88 RDI: 0000000000000000 RBP: 0000000000000003 R08: 00007ffe0faf6fd0 R09: 0000000000000002 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000 R13: 00007ffe0faf7210 R14: 00007f4a27dbb000 R15: 00005576e2150d98 ------------[ cut here ]------------ rrln < 0 || rrln > RCU_NEST_PMAX WARNING: kernel/rcu/tree_plugin.h:443 at __rcu_read_unlock kernel/rcu/tree_plugin.h:443 [inline], CPU#2: dhcpcd-run-hook/5886 WARNING: kernel/rcu/tree_plugin.h:443 at __rcu_read_unlock+0x235/0x5e0 kernel/rcu/tree_plugin.h:430, CPU#2: dhcpcd-run-hook/5886 Modules linked in: CPU: 2 UID: 0 PID: 5886 Comm: dhcpcd-run-hook Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__rcu_read_unlock kernel/rcu/tree_plugin.h:443 [inline] RIP: 0010:__rcu_read_unlock+0x235/0x5e0 kernel/rcu/tree_plugin.h:430 Code: 74 11 c7 45 58 01 00 00 00 bf 09 00 00 00 e8 d2 70 da ff e8 cd fd 22 00 9c 58 f6 c4 02 0f 85 dd 02 00 00 fb e9 57 fe ff ff 90 <0f> 0b 90 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc e8 a4 74 88 RSP: 0018:ffffc90003387778 EFLAGS: 00010286 RAX: 00000000ffffffff RBX: ffff888025320000 RCX: ffffffff81e8a36e RDX: 0000000000000000 RSI: ffffffff8df30d5f RDI: ffff8880253204c4 RBP: 0000000000000004 R08: 0000000000000005 R09: 0000000000000000 R10: 0000000080000000 R11: 0000000000000001 R12: ffff88802b94b9b8 R13: fffffbfff21b8360 R14: 0000000000000000 R15: 00007f4a27cba000 FS: 0000000000000000(0000) GS:ffff8880d64e7000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffe0faf6018 CR3: 0000000037c7b000 CR4: 0000000000352ef0 Call Trace: rcu_read_unlock include/linux/rcupdate.h:871 [inline] pte_unmap include/linux/pgtable.h:117 [inline] zap_pte_range mm/memory.c:1948 [inline] zap_pmd_range mm/memory.c:2004 [inline] zap_pud_range mm/memory.c:2032 [inline] zap_p4d_range mm/memory.c:2053 [inline] __zap_vma_range+0x22e6/0x4bf0 mm/memory.c:2093 unmap_vmas+0x299/0x5f0 mm/memory.c:2162 exit_mmap+0x1ef/0xa10 mm/mmap.c:1300 __mmput+0x12a/0x410 kernel/fork.c:1178 mmput+0x67/0x80 kernel/fork.c:1201 exit_mm kernel/exit.c:581 [inline] do_exit+0x833/0x2a60 kernel/exit.c:963 do_group_exit+0xd5/0x2a0 kernel/exit.c:1117 __do_sys_exit_group kernel/exit.c:1128 [inline] __se_sys_exit_group kernel/exit.c:1126 [inline] __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1126 x64_sys_call+0x102c/0x1530 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x10b/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f4a27bab6c5 Code: Unable to access opcode bytes at 0x7f4a27bab69b. RSP: 002b:00007ffe0faf6ed8 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007ffe0faf7104 RCX: 00007f4a27bab6c5 RDX: 00000000000000e7 RSI: ffffffffffffff88 RDI: 0000000000000000 RBP: 0000000000000003 R08: 00007ffe0faf6fd0 R09: 0000000000000002 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000 R13: 00007ffe0faf7210 R14: 00007f4a27dbb000 R15: 00005576e2150d98 --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup