panic: trap type NUM, code=NUM, pc=3c7a9

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7e284d508f03 Fix capping of VAPs
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=102c3f8d180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=cdfb6150d2e4fd11191c

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3d84a812217b/disk-7e284d50.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/ac9820587c99/bsd-7e284d50.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/66ed180922d4/kernel-7e284d50.xz

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

panic: trap type 6, code=10, pc=3c7a9
Starting stack trace...
panic(ffffffff828495b1) at panic+0x16f sys/kern/subr_prf.c:229
kerntrap(ffff800033d782f0) at kerntrap+0x1d7 sys/arch/amd64/amd64/trap.c:327
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
acpi_pdirpa() at acpi_pdirpa+0x2861a
rt_clone(ffff800033d785c8,fffffd8063ecc9e8,0) at rt_clone+0x7d sys/net/route.c:383
route_mpath(fffffd8063ecc9d0,fffffd805ede9624,0,0) at route_mpath+0x112 rt_match sys/net/route.c:360 [inline]
route_mpath(fffffd8063ecc9d0,fffffd805ede9624,0,0) at route_mpath+0x112 rtalloc_mpath sys/net/route.c:476 [inline]
route_mpath(fffffd8063ecc9d0,fffffd805ede9624,0,0) at route_mpath+0x112 sys/net/route.c:255
in_pcbselsrc(ffff800033d786b8,fffffd805ede9620,fffffd8063ecc958) at in_pcbselsrc+0x1b7 sys/netinet/in_pcb.c:980
in_pcbconnect(fffffd8063ecc958,fffffd805ede9600) at in_pcbconnect+0xe8 sys/netinet/in_pcb.c:523
udp_connect(ffff800000e7fdb0,fffffd805ede9600) at udp_connect+0xa4 sys/netinet/udp_usrreq.c:1196
sys_connect(ffff800033dab4e8,ffff800033d788b0,ffff800033d78800) at sys_connect+0x239 sys/kern/uipc_syscalls.c:422
syscall(ffff800033d788b0) at syscall+0x8cf mi_syscall sys/sys/syscall_mi.h:180 [inline]
syscall(ffff800033d788b0) at syscall+0x8cf sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x821fe7e90d0, count: 245
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 50375c3b-e826-8a7e-06ca-b163c863336b
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 0x000f27f0: 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.65
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