[syzbot] upstream boot error: BUG: unable to handle kernel paging request in gic_handle_irq

syzbot
2023-04-29T13:37:45Z

Hello,

syzbot found the following issue on:

HEAD commit: cec24b8b6bb8 Merge tag 'char-misc-6.4-rc1' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11334c30280000
kernel config: https://syzkaller.appspot.com/x/.config?x=c159a5b5ee7dcf56
dashboard link: https://syzkaller.appspot.com/bug?extid=4aee2040dfac273d198e
compiler: arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4aee2040dfac273d198e@syzkaller.appspotmail.com

8<--- cut here ---
Unable to handle kernel paging request at virtual address df80a00c when read
[df80a00c] *pgd=80000080007003, *pmd=82893003, *pte=80216680
Internal error: Oops: 207 [#1] PREEMPT SMP ARM
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.3.0-syzkaller #0
Hardware name: ARM-Versatile Express
PC is at __raw_readl arch/arm/include/asm/io.h:113 [inline]
PC is at gic_handle_irq+0x1c/0x7c drivers/irqchip/irq-gic.c:344
LR is at generic_handle_arch_irq+0x60/0x80 kernel/irq/handle.c:238
pc : [<8086e724>] lr : [<817e3dd0>] psr: 20000193
sp : 82401e70 ip : 82401e90 fp : 82401e8c
r10: 825dfffd r9 : 8241ae40 r8 : 00000000
r7 : df80a00c r6 : 81f1590c r5 : df80a000 r4 : 8240cde8
r3 : 8086e708 r2 : 00904870 r1 : 81f4ff24 r0 : 82401eb8
Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
Control: 30c5387d Table: 80003000 DAC: fffffffd
Register r0 information:
8<--- cut here ---
Unable to handle kernel paging request at virtual address fffffff7 when read
[fffffff7] *pgd=80000080007003, *pmd=deffd003, *pte=00000000
Internal error: Oops: 207 [#2] PREEMPT SMP ARM

---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup