panic: kernel diagnostic assertion "uvm_page_owner_locked_p(pg)" failed

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3c9ccb50785e vio: Increase rx mbuf size with lro
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=16203527980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=9a71359b255499520743

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f523a5b99cd4/disk-3c9ccb50.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/6933bd6dea80/bsd-3c9ccb50.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b0e198f764a6/kernel-3c9ccb50.xz

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

panic: kernel diagnostic assertion "uvm_page_owner_locked_p(pg)" failed
: file "/syzkaller/managers/main/kernel/sys/uvm/uvm_page.c", line 1248
Starting stack trace...
panic(ffffffff830b5564) at panic+0x1ba sys/kern/subr_prf.c:229
__assert(ffffffff83068477,ffffffff82fba2dc,4e0,ffffffff830bd7bc) at __assert+0x29
uvm_pageunwire(fffffd8006956480) at uvm_pageunwire+0x1dd sys/uvm/uvm_page.c:1248
uvm_fault_unwire_locked(fffffd806313dd88,dfc24f17000,dfc25116000) at uvm_fault_unwire_locked+0x33e sys/uvm/uvm_fault.c:1695
uvm_unmap_kill_entry_withlock(fffffd806313dd88,fffffd80762d80b8,0) at uvm_unmap_kill_entry_withlock+0x81 sys/uvm/uvm_map.c:1861
uvm_map_teardown(fffffd806313dd88) at uvm_map_teardown+0x1c7 sys/uvm/uvm_map.c:2498
uvmspace_free(fffffd806313dd88) at uvmspace_free+0xbd sys/uvm/uvm_map.c:3422
reaper(ffff80002a457be0) at reaper+0x225 sys/kern/kern_exit.c:481
end trace frame: 0x0, count: 249
End of stack 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

[syzbot]

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