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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8e9d9dd5c33e nfsm_srvnamesiz() may set up an NFSERR_NAMETO..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1555249f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=1d2b4724759b9382f913

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/83b7ffd94945/disk-8e9d9dd5.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/c8d0c65eb208/bsd-8e9d9dd5.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a32b4b7ce3c2/kernel-8e9d9dd5.xz

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

panic: trap type 6, code=10, pc=e9779
Starting stack trace...
panic(ffffffff82fd7e86) at panic+0x1d0 sys/kern/subr_prf.c:229
kerntrap(ffff80003624ea20) at kerntrap+0x29b sys/arch/amd64/amd64/trap.c:327
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
acpi_pdirpa() at acpi_pdirpa+0xd55ea
rt_clone(ffff80003624ecf8,ffff80003624edf8,0) at rt_clone+0x98 sys/net/route.c:383
route_mpath(ffff80003624ede0,fffffd806cdaa1f0,fffffd806cdaa1ec,0) at route_mpath+0x170 rt_match sys/net/route.c:360 [inline]
route_mpath(ffff80003624ede0,fffffd806cdaa1f0,fffffd806cdaa1ec,0) at route_mpath+0x170 rtalloc_mpath sys/net/route.c:476 [inline]
route_mpath(ffff80003624ede0,fffffd806cdaa1f0,fffffd806cdaa1ec,0) at route_mpath+0x170 sys/net/route.c:255
in_ouraddr(fffffd806cdaa100,ffff800001193800,ffff80003624ede0,9) at in_ouraddr+0xc2
ip_input_if(ffff80003624eed8,ffff80003624eee4,ffff800030777000,0,ffff800001193800) at ip_input_if+0x422 sys/netinet/ip_input.c:508
ipv4_input(ffff800001193800,fffffd806cdaa100) at ipv4_input+0x50 sys/netinet/ip_input.c:337
ether_input(ffff800001193800,fffffd806cdaa100) at ether_input+0x6e4
tun_dev_write(5d02,ffff80003624f258,ffff800030777000,2) at tun_dev_write+0x301 sys/net/if_tun.c:914
spec_write(ffff80003624f0b0) at spec_write+0x120 sys/kern/spec_vnops.c:302
VOP_WRITE(fffffd806d0d7388,ffff80003624f258,11,fffffd807f7d35b0) at VOP_WRITE+0x102 sys/kern/vfs_vops.c:245
vn_write(fffffd807807e4e0,ffff80003624f258,0) at vn_write+0x1d1 sys/kern/vfs_vnops.c:408
dofilewritev(ffff8000ffffc298,c8,ffff80003624f258,0,ffff80003624f310) at dofilewritev+0x23c sys/kern/sys_generic.c:380
sys_write(ffff8000ffffc298,ffff80003624f3c0,ffff80003624f310) at sys_write+0xa2 sys/kern/sys_generic.c:300
syscall(ffff80003624f3c0) at syscall+0xbb6 mi_syscall sys/sys/syscall_mi.h:179 [inline]
syscall(ffff80003624f3c0) at syscall+0xbb6 sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xbecd1fb4ca0, 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 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