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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 25b30cac31a3 sort
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=149e77fb180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=843621263fed1456ca89

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a2564b1f7252/disk-25b30cac.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/319d6a006bad/bsd-25b30cac.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1162abc82f00/kernel-25b30cac.xz

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

panic: trap type 6, code=10, pc=3c709
Starting stack trace...
panic(ffffffff82854593) at panic+0x16f sys/kern/subr_prf.c:229
kerntrap(ffff80002a249eb0) at kerntrap+0x1d7 sys/arch/amd64/amd64/trap.c:327
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
acpi_pdirpa() at acpi_pdirpa+0x2857a
rt_clone(ffff80002a24a188,ffff80002a24a1f8,0) at rt_clone+0x7d sys/net/route.c:383
rtalloc_mpath(ffff80002a24a1f8,fffffd806d0598ec,0) at rtalloc_mpath+0xbc rt_match sys/net/route.c:360 [inline]
rtalloc_mpath(ffff80002a24a1f8,fffffd806d0598ec,0) at rtalloc_mpath+0xbc sys/net/route.c:476
in_ouraddr(fffffd806d059800,ffff800000dfc000,ffff80002a24a288) at in_ouraddr+0xab sys/netinet/ip_input.c:833
ip_input_if(ffff80002a24a338,ffff80002a24a344,ffff80002a294000,0,ffff800000dfc000) at ip_input_if+0x27e sys/netinet/ip_input.c:485
ipv4_input(ffff800000dfc000,fffffd806d059800) at ipv4_input+0x47 sys/netinet/ip_input.c:327
ether_input(ffff800000dfc000,fffffd806d059800) at ether_input+0x525
tun_dev_write(5d05,ffff80002a24a6b8,ffff80002a294000,2) at tun_dev_write+0x209 sys/net/if_tun.c:914
spec_write(ffff80002a24a510) at spec_write+0xe1 sys/kern/spec_vnops.c:302
VOP_WRITE(fffffd806b609dd8,ffff80002a24a6b8,11,fffffd807f7d76e8) at VOP_WRITE+0xc3 sys/kern/vfs_vops.c:245
vn_write(fffffd806ee77a20,ffff80002a24a6b8,0) at vn_write+0x15c sys/kern/vfs_vnops.c:408
dofilewritev(ffff80002bc9d4d0,c8,ffff80002a24a6b8,0,ffff80002a24a770) at dofilewritev+0x1a9 sys/kern/sys_generic.c:375
sys_write(ffff80002bc9d4d0,ffff80002a24a820,ffff80002a24a770) at sys_write+0x87 sys/kern/sys_generic.c:295
syscall(ffff80002a24a820) at syscall+0x8cf mi_syscall sys/sys/syscall_mi.h:180 [inline]
syscall(ffff80002a24a820) at syscall+0x8cf sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x9f15a7af1e0, count: 239
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 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