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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 33482ba5f7b4 Teach symbols test about the namespace
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1017bbb9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=f9f24508aa4fdaa31559

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/97b88c53f9ef/disk-33482ba5.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/eaecfa36104d/bsd-33482ba5.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cf66aec84224/kernel-33482ba5.xz

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

panic: trap type 6, code=10, pc=e6d59
Starting stack trace...
panic(ffffffff82f98954) at panic+0x1ba sys/kern/subr_prf.c:229
kerntrap(ffff800037708cf0) at kerntrap+0x28b sys/arch/amd64/amd64/trap.c:327
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
acpi_pdirpa() at acpi_pdirpa+0xd2bca
rt_match(ffff8000377090c0,0,1,0) at rt_match+0xf0 rt_clone sys/net/route.c:383 [inline]
rt_match(ffff8000377090c0,0,1,0) at rt_match+0xf0 sys/net/route.c:358

route_mpath(ffff8000377090a8,fffffd806c154ee8,fffffd806c154ee4,0) at route_mpath+0xb8 sys/net/route.c:255
in_ouraddr(fffffd806c154e00,ffff80000116d800,ffff8000377090a8,0) at in_ouraddr+0xc2
ip_input_if(ffff800037709198,ffff8000377091a4,ffff80002d3dc000,0,ffff80000116d800) at ip_input_if+0x3dd sys/netinet/ip_input.c:498
ipv4_input(ffff80000116d800,fffffd806c154e00) at ipv4_input+0x50 sys/netinet/ip_input.c:327
ether_input(ffff80000116d800,fffffd806c154e00) at ether_input+0x6e4
tun_dev_write(5d00,ffff800037709518,ffff80002d3dc000,2) at tun_dev_write+0x301 sys/net/if_tun.c:914
spec_write(ffff800037709370) at spec_write+0x117 sys/kern/spec_vnops.c:302
VOP_WRITE(fffffd806aea21f8,ffff800037709518,11,fffffd807f7d7750) at VOP_WRITE+0x102 sys/kern/vfs_vops.c:245
vn_write(fffffd807e395900,ffff800037709518,0) at vn_write+0x1c3 sys/kern/vfs_vnops.c:408
dofilewritev(ffff80002a4c62a0,c8,ffff800037709518,0,ffff8000377095d0) at dofilewritev+0x23c sys/kern/sys_generic.c:375
sys_write(ffff80002a4c62a0,ffff800037709680,ffff8000377095d0) at sys_write+0xa2 sys/kern/sys_generic.c:295
syscall(ffff800037709680) at syscall+0x97e sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x2776be53ac0, 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 1f64d870-06f2-d8bf-7327-adc6877a2997
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 $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