[syzbot] upstream boot error: BUG: unable to handle kernel NULL pointer dereference in __irq_resolve_mapping

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 348551ddaf31 Merge tag 'pinctrl-v6.4-1' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14398ef8280000
kernel config: https://syzkaller.appspot.com/x/.config?x=124f13edd5df0b0d
dashboard link: https://syzkaller.appspot.com/bug?extid=ed37e5e7af93ae8a08ba
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+ed37e5...@syzkaller.appspotmail.com

8<--- cut here ---
Unable to handle kernel NULL pointer dereference at virtual address 00000213 when read
[00000213] *pgd=80000080004003, *pmd=00000000
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 irq_data_to_desc include/linux/irqdesc.h:124 [inline]
PC is at __irq_resolve_mapping+0x40/0x90 kernel/irq/irqdomain.c:968
LR is at rcu_read_lock include/linux/rcupdate.h:771 [inline]
LR is at __irq_resolve_mapping+0x20/0x90 kernel/irq/irqdomain.c:960
pc : [<802c0dec>] lr : [<802c0dcc>] psr: 20000193
sp : 82601e58 ip : 82601e58 fp : 82601e74
r10: 00000000 r9 : 8261ae40 r8 : 00000000
r7 : df80a00c r6 : 00000000 r5 : 0000001b r4 : 83094000
r3 : 83094060 r2 : 8261ae40 r1 : 0000001b r0 : 00000207
Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
Control: 30c5387d Table: 848c1880 DAC: fffffffd
Register r0 information: non-paged memory
Register r1 information: non-paged memory
Register r2 information: non-slab/vmalloc memory
Register r3 information:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 0 at mm/slub.c:4649 __kmem_obj_info+0x1c4/0x21c mm/slub.c:4649
Modules linked in:


---
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 syzk...@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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.