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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e298eee01736 sync
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=17791d82980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=f188720692d71dabaa86

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/47092e314e07/disk-e298eee0.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/616f2fa5dec5/bsd-e298eee0.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84625ff9519a/kernel-e298eee0.xz

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

panic: trap type 6, code=10, pc=3ca79
Starting stack trace...
panic(ffffffff82852286) at panic+0x16f sys/kern/subr_prf.c:229
kerntrap(ffff80002bb4ac10) at kerntrap+0x1d7 sys/arch/amd64/amd64/trap.c:327
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
acpi_pdirpa() at acpi_pdirpa+0x288ea
rt_clone(ffff80002bb4aee8,ffff80002bb4afe0,0) at rt_clone+0x7d sys/net/route.c:383
route_mpath(ffff80002bb4afc8,fffffd8075aaece8,fffffd8075aaece4,0) at route_mpath+0x112 rt_match sys/net/route.c:360 [inline]
route_mpath(ffff80002bb4afc8,fffffd8075aaece8,fffffd8075aaece4,0) at route_mpath+0x112 rtalloc_mpath sys/net/route.c:476 [inline]
route_mpath(ffff80002bb4afc8,fffffd8075aaece8,fffffd8075aaece4,0) at route_mpath+0x112 sys/net/route.c:255
in_ouraddr(fffffd8075aaec00,ffff800000e97800,ffff80002bb4afc8) at in_ouraddr+0x98 sys/netinet/ip_input.c:831
ip_input_if(ffff80002bb4b0b8,ffff80002bb4b0c4,ffff80002f74b000,0,ffff800000e97800) at ip_input_if+0x28e sys/netinet/ip_input.c:486
ipv4_input(ffff800000e97800,fffffd8075aaec00) at ipv4_input+0x47 sys/netinet/ip_input.c:327
ether_input(ffff800000e97800,fffffd8075aaec00) at ether_input+0x527
tun_dev_write(5d04,ffff80002bb4b438,ffff80002f74b000,2) at tun_dev_write+0x209 sys/net/if_tun.c:914
spec_write(ffff80002bb4b290) at spec_write+0xe1 sys/kern/spec_vnops.c:302
VOP_WRITE(fffffd80684397f0,ffff80002bb4b438,11,fffffd807f7d3410) at VOP_WRITE+0xc3 sys/kern/vfs_vops.c:245
vn_write(fffffd8068fcb740,ffff80002bb4b438,0) at vn_write+0x15c sys/kern/vfs_vnops.c:408
dofilewritev(ffff80002a2174b8,c8,ffff80002bb4b438,0,ffff80002bb4b4f0) at dofilewritev+0x1a9 sys/kern/sys_generic.c:375
sys_write(ffff80002a2174b8,ffff80002bb4b5a0,ffff80002bb4b4f0) at sys_write+0x87 sys/kern/sys_generic.c:295
syscall(ffff80002bb4b5a0) at syscall+0x8cf mi_syscall sys/sys/syscall_mi.h:180 [inline]
syscall(ffff80002bb4b5a0) at syscall+0x8cf sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xd938709e500, 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 479bd2e4-6073-186a-8c25-a69e4074584d
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