From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f78.google.com (mail-oo1-f78.google.com [209.85.161.78]) (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 40B0D311C11 for ; Sun, 26 Apr 2026 08:17:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.78 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777191447; cv=none; b=PNZUMlRY6Ca3CYEvGBCNRCcVkMP6yqmPCbvO6fQXpT7W4MLVDaT7F4E/32Vpjzg2DQpGq+1UZYOmYiHTfy7YrARQ+2/XF0iPtRvR0Sbn8yy/BXufT+ze8WF8avCH5+cX0GW3rkS3H3zMFaQ5NQ6D05nJquyoEjEjURV8fxNZmPc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777191447; c=relaxed/simple; bh=L9l8ejbK8/Tjw7HeBoVBXtEBj1c371SmmeXlQmOoDC0=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=XJyFQsR/c2Sdk9jmLwriJ7ZicMXi6X5+08RNRnk+GMluGvA09lvp4mB3Dbdt6hdPRhQDZV+WlSdBGztyL9W8NZizzpuajQW4FVY5o0InAJxy/tZe/SG/BBEK97qHYTDK2OXx1Yj28GMhRQL0R+jZi62JOtTuze3M5oDwS6aHV8A= 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.78 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-f78.google.com with SMTP id 006d021491bc7-672c40f3873so19257807eaf.2 for ; Sun, 26 Apr 2026 01:17:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777191445; x=1777796245; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=abpl5VjWxNF871HT77D7jiqQ5tPgHx4siodqZ1Cbc4o=; b=eUnAPF2fYS4Ag84UggM9LAE9hAM/4qF4c6OShRM+yx0TEuQZ0AngmuV6aWOMl8Eg7c XtQ7ILaDNOdqXhLjgYC3oerUW0Hh4smhEsgbBykShWGGJFCXQreSQI68uDOao5l6E0QE uIJqu17PqXSPdiPRp2MrsIxveuCqHa1WAo3AaQQEM6UINIZDiMImWYceZa4KYGg9hEII l0Pt39JDNsOk5dj09GlOcKOIva+3a4Ats3cSNzXrDU4it0JtXyNfjrwuMkQ3/GW7lMZZ 1B5zs2P203YcxKvxKuZjb1FCANRGNhWv4j7ldgmJgdE2cA7EnCsFM9mn9wtbxCqLxPyf Ui5Q== X-Forwarded-Encrypted: i=1; AFNElJ/xtIEbjryohrN7Ln6a9pJ4GLq77XNeJ1Os+TXXirlcYclYayCQuAEC2aycEiW9n9KVwdncb8lHs8nYrNg=@vger.kernel.org X-Gm-Message-State: AOJu0YzNythYafGcCRSkzSDZ/D+N3s6cMXYl4TxuFIGAU0IGhdsiiz1Q w2BA9Ad2MIY9qEnjc99sdq8wlp/PFW4lLIpZC9LkaFW14F5OUsQe6i8ZR2OqafO9k/hKbegZ6IS /8GwBYvuAX0wbSZbJnKKtqFLyBnPsm0zt2pTHgt3ki0TenD78+MuUx66ZcKQ= 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:4b14:b0:696:25d4:1e62 with SMTP id 006d021491bc7-69625d42208mr5229115eaf.2.1777191445302; Sun, 26 Apr 2026 01:17:25 -0700 (PDT) Date: Sun, 26 Apr 2026 01:17:25 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69edca15.170a0220.38e3f1.0000.GAE@google.com> Subject: [syzbot] [mm?] WARNING: bad unlock balance in do_wp_page From: syzbot To: Liam.Howlett@oracle.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org, shakeel.butt@linux.dev, surenb@google.com, syzkaller-bugs@googlegroups.com, vbabka@kernel.org Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 6596a02b2078 Merge tag 'drm-next-2026-04-22' of https://gi.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12483702580000 kernel config: https://syzkaller.appspot.com/x/.config?x=24c8da4692f901cb dashboard link: https://syzkaller.appspot.com/bug?extid=7d60b33a8a546263da7c compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 userspace arch: i386 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-6596a02b.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/c5a50c04af50/vmlinux-6596a02b.xz kernel image: https://storage.googleapis.com/syzbot-assets/70da0dbf8561/bzImage-6596a02b.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+7d60b33a8a546263da7c@syzkaller.appspotmail.com ===================================== WARNING: bad unlock balance detected! syzkaller #0 Not tainted ------------------------------------- dhcpcd-run-hook/5941 is trying to release lock (rcu_read_lock) at: [] rcu_read_unlock+0x2d/0xb0 include/linux/rcupdate.h:867 but there are no more locks to release! other info that might help us debug this: 1 lock held by dhcpcd-run-hook/5941: #0: ffff8880440f3d48 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x11d/0x590 mm/mmap_lock.c:310 stack backtrace: CPU: 2 UID: 0 PID: 5941 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_read_unlock+0x32/0xb0 include/linux/rcupdate.h:867 pte_unmap include/linux/pgtable.h:117 [inline] wp_page_copy mm/memory.c:3960 [inline] do_wp_page+0x13d7/0x4350 mm/memory.c:4320 handle_pte_fault mm/memory.c:6427 [inline] __handle_mm_fault+0x1ab6/0x2a00 mm/memory.c:6549 handle_mm_fault+0x36d/0xa20 mm/memory.c:6718 do_user_addr_fault+0x5a3/0x12f0 arch/x86/mm/fault.c:1334 handle_page_fault arch/x86/mm/fault.c:1474 [inline] exc_page_fault+0x6f/0xd0 arch/x86/mm/fault.c:1527 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618 RIP: 0033:0x7f7501c33f87 Code: 5c 25 28 49 8b 57 10 48 85 db 74 27 8b 74 24 0c 23 73 08 44 39 f6 75 16 48 39 c2 75 05 e8 62 ff ff ff 48 8b 53 10 48 83 c0 08 <48> 89 50 f8 48 8b 1b eb d0 49 83 c4 08 49 81 fc 38 01 00 00 75 be RSP: 002b:00007ffd29921270 EFLAGS: 00010212 RAX: 00005645dcc81140 RBX: 00005645dcc716d0 RCX: 0000000000000002 RDX: 00007ffd29925f83 RSI: 0000000000000001 RDI: 0000000000000001 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000008 R13: 00005645dcc70e60 R14: 0000000000000001 R15: 00005645dcc70c30 ------------[ 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#3: dhcpcd-run-hook/5941 WARNING: kernel/rcu/tree_plugin.h:443 at __rcu_read_unlock+0x235/0x5e0 kernel/rcu/tree_plugin.h:430, CPU#3: dhcpcd-run-hook/5941 Modules linked in: CPU: 3 UID: 0 PID: 5941 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 12 a5 da ff e8 9d e2 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 e9 d9 14 ad 09 e8 44 64 87 RSP: 0000:ffffc900049c7af0 EFLAGS: 00010286 RAX: 00000000ffffffff RBX: ffff888029ec4a00 RCX: ffffffff81e80bfe RDX: 0000000000000000 RSI: ffffffff8df2fec2 RDI: ffff888029ec4ec4 RBP: 0000000000000001 R08: 0000000000000005 R09: 0000000000000000 R10: 0000000080000000 R11: 0000000000000012 R12: ffff88802ad93408 R13: ffffea0000ad7800 R14: 0000000000000000 R15: ffffea0000ad7800 FS: 00007f7501945c80(0000) GS:ffff8880973e2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005645dcc70950 CR3: 00000000297d6000 CR4: 0000000000352ef0 Call Trace: pte_unmap include/linux/pgtable.h:117 [inline] wp_page_copy mm/memory.c:3960 [inline] do_wp_page+0x13d7/0x4350 mm/memory.c:4320 handle_pte_fault mm/memory.c:6427 [inline] __handle_mm_fault+0x1ab6/0x2a00 mm/memory.c:6549 handle_mm_fault+0x36d/0xa20 mm/memory.c:6718 do_user_addr_fault+0x5a3/0x12f0 arch/x86/mm/fault.c:1334 handle_page_fault arch/x86/mm/fault.c:1474 [inline] exc_page_fault+0x6f/0xd0 arch/x86/mm/fault.c:1527 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618 RIP: 0033:0x7f7501c33f87 Code: 5c 25 28 49 8b 57 10 48 85 db 74 27 8b 74 24 0c 23 73 08 44 39 f6 75 16 48 39 c2 75 05 e8 62 ff ff ff 48 8b 53 10 48 83 c0 08 <48> 89 50 f8 48 8b 1b eb d0 49 83 c4 08 49 81 fc 38 01 00 00 75 be RSP: 002b:00007ffd29921270 EFLAGS: 00010212 RAX: 00005645dcc81140 RBX: 00005645dcc716d0 RCX: 0000000000000002 RDX: 00007ffd29925f83 RSI: 0000000000000001 RDI: 0000000000000001 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000008 R13: 00005645dcc70e60 R14: 0000000000000001 R15: 00005645dcc70c30 --- 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