panic:smr: dispatch took NUM.ADDRs

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e294fe4a4b1d don't call pf_pkt_addr_changed, it's not need..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=10fc09b4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=0ce5f490f2a4f426feda

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b02a3a17bc4c/disk-e294fe4a.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/5795c3449541/bsd-e294fe4a.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/19c7c86b27f7/kernel-e294fe4a.xz

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

panic:smr: dispatch took 3.480000s


---
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