panic: trap type NUM, code=NUM, pc=e94f9

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d05e5827ac65 document the mlkem768x25519-sha256 key exchan..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1149a807980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=77c3993693decdaa452d

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/05de8258375b/disk-d05e5827.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/dff5bddcaf87/bsd-d05e5827.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9f7a54b8c738/kernel-d05e5827.xz

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

panic: trap type 6, code=10, pc=e94f9
Starting stack trace...
panic(ffffffff82fdc33e) at panic+0x1d0 sys/kern/subr_prf.c:229
kerntrap(ffff800035d9f790) at kerntrap+0x29b sys/arch/amd64/amd64/trap.c:327
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
acpi_pdirpa() at acpi_pdirpa+0xd536a
rt_clone(ffff800035d9fa68,fffffd8079673200,0) at rt_clone+0x98 sys/net/route.c:383
route_mpath(fffffd80796731e8,ffff800035d9fbbc,0,0) at route_mpath+0x170 rt_match sys/net/route.c:360 [inline]
route_mpath(fffffd80796731e8,ffff800035d9fbbc,0,0) at route_mpath+0x170 rtalloc_mpath sys/net/route.c:476 [inline]
route_mpath(fffffd80796731e8,ffff800035d9fbbc,0,0) at route_mpath+0x170 sys/net/route.c:255
in_pcbselsrc(fffffd805bc9b0f4,ffff800035d9fbb8,fffffd8079673170) at in_pcbselsrc+0x250
rip_output(fffffd80788dbf00,ffff800010fdad08,ffff800035d9fbb8,467f) at rip_output+0x2bf sys/netinet/raw_ip.c:310
rip_send(ffff800010fdad08,fffffd80788dbf00,0,0) at rip_send+0x13d sys/netinet/raw_ip.c:628
sosend(ffff800010fdad08,0,ffff800035d9fdb8,0,0,0) at sosend+0xa40
dofilewritev(ffff800035f8fc10,3,ffff800035d9fdb8,0,ffff800035d9fe70) at dofilewritev+0x23c sys/kern/sys_generic.c:380
sys_write(ffff800035f8fc10,ffff800035d9ff20,ffff800035d9fe70) at sys_write+0xa2 sys/kern/sys_generic.c:300
syscall(ffff800035d9ff20) at syscall+0xbb6 mi_syscall sys/sys/syscall_mi.h:179 [inline]
syscall(ffff800035d9ff20) at syscall+0xbb6 sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x37a2abe3cf0, count: 243
End of stack trace.

dump to dev 4,1 not possible
rebooting...
SeaBIOS (version 1.8.2-google)
Total RAM Size = 0x0000000080000000 = 2048 MiB
CPUs found: 2 Max CPUs supported: 2
SeaBIOS (version 1.8.2-google)
Machine UUID 0d5ef51b-0062-dd1a-a10b-15f17b148763
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f27c0: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Sending Seabios boot VM event.
Booting from Hard Disk 0...
>> OpenBSD/amd64 BOOT 3.67
boot> set $lines = 0
set: syntax error
boot> set $maxwidth = 0
set: syntax error
boot> show panic
boot: illegal argument panic
boot> trace
boot> show registers
boot> show proc
boot> ps
boot> show all locks
boot> show malloc
boot> show all pools
boot> machine ddbcpu 0
machine: syntax error
boot> trace
boot> machine ddbcpu 1
machine: syntax error
boot> trace


---
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 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