panic: pfi_dynaddr_update

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 5837d48b Make vmd(8)'s ns8250 emulation more correct
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=13ad0c4aa00000
kernel config: https://syzkaller.appspot.com/x/.config?x=60e2b7157576c8d7
dashboard link: https://syzkaller.appspot.com/bug?extid=e7c998ef998bc8a73409

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

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

panic: pfi_dynaddr_update
Stopped at db_enter+0x18: addq $0x8,%rsp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
db_enter() at db_enter+0x18 sys/arch/amd64/amd64/db_interface.c:398
panic() at panic+0x15c sys/kern/subr_prf.c:212
pfi_kif_update(ffff8000009a4e00) at pfi_kif_update+0x17a sys/net/pf_if.c:440
pfi_detach_ifnet(ffff8000009de000) at pfi_detach_ifnet+0x4d
sys/net/pf_if.c:255
if_detach(ffff8000009de000) at if_detach+0x15d sys/net/if.c:1118
tun_clone_destroy(ffff8000009de000) at tun_clone_destroy+0x1c6
sys/net/if_tun.c:278
spec_close(ffff800015a027d8) at spec_close+0x3b0 sys/kern/spec_vnops.c:553
VOP_CLOSE(fffffd8038284538,2,fffffd803f7c6ba0,ffff8000ffff59d8) at
VOP_CLOSE+0x64 sys/kern/vfs_vops.c:174
vn_closefile(fffffd80300dfe98,ffff8000ffff59d8) at vn_closefile+0x14b
vn_close sys/kern/vfs_vnops.c:289 [inline]
vn_closefile(fffffd80300dfe98,ffff8000ffff59d8) at vn_closefile+0x14b
sys/kern/vfs_vnops.c:575
fdrop(fffffd80300dfe98,ffff8000ffff59d8) at fdrop+0xc9
sys/kern/kern_descrip.c:1260
closef(fffffd80300dfe98,ffff8000ffff59d8) at closef+0x118
sys/kern/kern_descrip.c:1244
fdfree(ffff8000ffff59d8) at fdfree+0xf7 sys/kern/kern_descrip.c:1176
exit1(ffff8000ffff59d8,0,1) at exit1+0x329 sys/kern/kern_exit.c:196
sys_exit(ffff8000ffff59d8,ffff800015a02a80,ffff800015a02af0) at
sys_exit+0x17 sys/kern/kern_exit.c:94
end trace frame: 0xffff800015a02b50, count: 0
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.