From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f77.google.com (mail-oo1-f77.google.com [209.85.161.77]) (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 B6198489888 for ; Sun, 2 Aug 2026 04:52:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.77 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785646351; cv=none; b=Dd6NFlEjqC+Tz41hrJus0d0Naijwqe5aaZY2S5taOdE6Yc5Slw1Y6qQVW84UaWqI0c6IL53Z2hUBuZaNHxeF32y+uz1LV6l9sC++yevYVeAr0/Ae/DKCNkXWyR2ijgMCS9hRVEbp33DXciT9tZDMHUe0aigTxPTiC1Q7qpsOjTg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785646351; c=relaxed/simple; bh=5SNb/Yp7a5MIAPXMzvrYwhRoVb33lNbV0pJuD9XQZbk=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=Rbn4tLHwdVRcw0ltOFm65bDhL9KScFxT/GqcLzV13wOgqOKM9p5NR4VZUY7Dgo6I6JwELIb28UgszgGXAVtr0xjM1UFlk2gPTA+Nndt5A5V1brDlH7xPtTzn/mBwwFbGzhjewwyun/4g+SCcYLnGP6CT/aHPVFmyQqOOiT9Kmog= 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.77 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-f77.google.com with SMTP id 006d021491bc7-6a17baa4d18so2561963eaf.1 for ; Sat, 01 Aug 2026 21:52:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1785646348; x=1786251148; h=content-type:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=ZSYWmd6PyKpvkGBJbHuqhKO6DfwJjPAGl+KvRnn72dI=; b=eDF+jKlkxLuzU61cwX/g9YufyRciY1k9ovO4ANDNiZYuzlQ+ikd3nAOwRXWkHRdT3F RlGVpL6a33PZk5j4weS4CkoiaFQtE8EKJ1ja6rhicqE2M/8ZBTC1vZrsSrhrbzvHUNlu t631DKH80Pdn47lOjsl9RDvrwONJk19NXt7tMMAOqVoQp6veXACmrz7XFUPKaz3Ebd4e Oscnhu39bTTZB1cWZZk2xnvD/tNIWfeUgZ1rvdAjuAXbMK/YoCSFJHAv4Mf9kz84AZOJ kIAyJ73bJTlCdhDq2iS7XnZPsn4df1vW03PceBS0fa3BckCJJjJIcIARDVE2mfO5LMZH WkRw== X-Forwarded-Encrypted: i=1; AHgh+RoixIdqUY34NIp/8iiKxqZtCTC1rTUS5uxTsplSN2RPNu3b60SnYUkXMnl2tikHNjoBGWNhMq4E2V+gdCk=@vger.kernel.org X-Gm-Message-State: AOJu0YyX2s/8UsCpHgjyoi56wdFDY/Oh2OZYiZaZAvRpURZ9xRJR3VHM HawUl7HEUlT8ooO9xhyTsiPt7Daoy9vU7Y/Ef79zVZ7wPtOIEuEbK/VVy9UciqtRPiMBwCtqPRE NcVUnakitJ2U/OLomfEBQ2xgIJKFPXOjuB18PBXJfvrn64JMzNu3I+p4GKKU= 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:4c16:b0:6ac:b521:c420 with SMTP id 006d021491bc7-6ae432f0c91mr8986978eaf.21.1785646348726; Sat, 01 Aug 2026 21:52:28 -0700 (PDT) Date: Sat, 01 Aug 2026 21:52:28 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a6ecd0c.6ce73036.24301b.001c.GAE@google.com> Subject: [syzbot] [kernel?] BUG: unable to handle kernel paging request in write_comp_data From: syzbot To: boqun@kernel.org, linux-kernel@vger.kernel.org, mathieu.desnoyers@efficios.com, paulmck@kernel.org, peterz@infradead.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: a2cf4ef33184 Merge tag 'devicetree-fixes-for-7.2' of git:/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=16c0cc9e580000 kernel config: https://syzkaller.appspot.com/x/.config?x=f221a1b5d497ed15 dashboard link: https://syzkaller.appspot.com/bug?extid=237f670105a254a230d4 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: https://storage.googleapis.com/syzbot-assets/6eb03d1a0722/disk-a2cf4ef3.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/4e0d90b14d28/vmlinux-a2cf4ef3.xz kernel image: https://storage.googleapis.com/syzbot-assets/9b81b6ecaa65/bzImage-a2cf4ef3.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+237f670105a254a230d4@syzkaller.appspotmail.com BUG: unable to handle page fault for address: ffffc90013ccbfe8 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 13fe60067 P4D 13fe60067 PUD 1cafa067 PMD 61350067 PTE 0 Oops: Oops: 0002 [#1] SMP KASAN PTI CPU: 0 UID: 0 PID: 19114 Comm: syz.3.1830 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 RIP: 0010:write_comp_data+0x75/0x90 kernel/kcov.c:267 Code: 00 8b bf fc 16 00 00 48 8b 30 48 c1 e7 03 4c 8d 1c b5 00 00 00 00 4a 8d 14 dd 28 00 00 00 48 39 d7 72 bd 48 83 c6 01 48 89 30 <4c> 89 44 10 e0 4c 89 4c 10 e8 4c 89 54 10 f0 4a 89 4c d8 20 c3 cc RSP: 0018:ffffc90005a57e78 EFLAGS: 00050257 RAX: ffffc90013ccc000 RBX: 0000000000000000 RCX: ffffffff824589a5 RDX: 0000000000000008 RSI: 0000000000000000 RDI: 0000000000400000 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000002 R10: 0000000000000001 R11: fffffffffffffffc R12: 0000000000000020 R13: 0000000000000000 R14: 00007ffffffff000 R15: 0000000000000001 FS: 00007fa950b4b6c0(0000) GS:ffff888123de1000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc90013ccbfe8 CR3: 000000005848c000 CR4: 00000000003526f0 Call Trace: rseq_register+0x115/0x350 kernel/rseq.c:460 __do_sys_rseq kernel/rseq.c:561 [inline] __se_sys_rseq kernel/rseq.c:547 [inline] __x64_sys_rseq+0x1b8/0x2e0 kernel/rseq.c:547 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x115/0x840 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fa95359e019 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:00007fa950b4b028 EFLAGS: 00000246 ORIG_RAX: 000000000000014e RAX: ffffffffffffffda RBX: 00007fa953826450 RCX: 00007fa95359e019 RDX: 0000000000000000 RSI: 0000000000000020 RDI: 0000000000000000 RBP: 00007fa95363500c R08: 0000000000000000 R09: 0000000000000000 R10: 000000000000000e R11: 0000000000000246 R12: 0000000000000000 R13: 00007fa9538264e8 R14: 00007fa953826450 R15: 00007fff4d0e3998 Modules linked in: CR2: ffffc90013ccbfe8 ---[ end trace 0000000000000000 ]--- RIP: 0010:write_comp_data+0x75/0x90 kernel/kcov.c:267 Code: 00 8b bf fc 16 00 00 48 8b 30 48 c1 e7 03 4c 8d 1c b5 00 00 00 00 4a 8d 14 dd 28 00 00 00 48 39 d7 72 bd 48 83 c6 01 48 89 30 <4c> 89 44 10 e0 4c 89 4c 10 e8 4c 89 54 10 f0 4a 89 4c d8 20 c3 cc RSP: 0018:ffffc90005a57e78 EFLAGS: 00050257 RAX: ffffc90013ccc000 RBX: 0000000000000000 RCX: ffffffff824589a5 RDX: 0000000000000008 RSI: 0000000000000000 RDI: 0000000000400000 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000002 R10: 0000000000000001 R11: fffffffffffffffc R12: 0000000000000020 R13: 0000000000000000 R14: 00007ffffffff000 R15: 0000000000000001 FS: 00007fa950b4b6c0(0000) GS:ffff888123de1000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc90013ccbfe8 CR3: 000000005848c000 CR4: 00000000003526f0 ---------------- Code disassembly (best guess): 0: 00 8b bf fc 16 00 add %cl,0x16fcbf(%rbx) 6: 00 48 8b add %cl,-0x75(%rax) 9: 30 48 c1 xor %cl,-0x3f(%rax) c: e7 03 out %eax,$0x3 e: 4c 8d 1c b5 00 00 00 lea 0x0(,%rsi,4),%r11 15: 00 16: 4a 8d 14 dd 28 00 00 lea 0x28(,%r11,8),%rdx 1d: 00 1e: 48 39 d7 cmp %rdx,%rdi 21: 72 bd jb 0xffffffe0 23: 48 83 c6 01 add $0x1,%rsi 27: 48 89 30 mov %rsi,(%rax) * 2a: 4c 89 44 10 e0 mov %r8,-0x20(%rax,%rdx,1) <-- trapping instruction 2f: 4c 89 4c 10 e8 mov %r9,-0x18(%rax,%rdx,1) 34: 4c 89 54 10 f0 mov %r10,-0x10(%rax,%rdx,1) 39: 4a 89 4c d8 20 mov %rcx,0x20(%rax,%r11,8) 3e: c3 ret 3f: cc int3 --- 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