assert "uvm_page_owner_locked_p(pg, TRUE)" failed in uvm_page.c

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1eab3ea7ad62 Clean-up BUILDINFO from /home/_sysupgrade lik..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=176bd724580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=09beba1b131af8d8235e

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8274bc1a3a81/disk-1eab3ea7.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/71eb2e96a3a7/bsd-1eab3ea7.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2073dec876bc/kernel-1eab3ea7.xz

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

panic: kernel diagnostic assertion "uvm_page_owner_locked_p(pg, TRUE)" failed: file "/syzkaller/managers/main/kernel/sys/uvm/uvm_page.c", line 1248
Starting stack trace...
panic(ffffffff8311d783) at panic+0x1ba sys/kern/subr_prf.c:229
__assert(ffffffff830d7289,ffffffff83025989,4e0,ffffffff8305b6f1) at __assert+0x29
uvm_pageunwire(fffffd80074f6a80) at uvm_pageunwire+0x1dd sys/uvm/uvm_page.c:1248
uvm_fault_unwire_locked(fffffd806c1e8cb8,c611ab55000,c611af54000) at uvm_fault_unwire_locked+0x33c sys/uvm/uvm_fault.c:1774
uvm_unmap_kill_entry_withlock(fffffd806c1e8cb8,fffffd805f410eb0,0) at uvm_unmap_kill_entry_withlock+0x81 sys/uvm/uvm_map.c:1860
uvm_map_teardown(fffffd806c1e8cb8) at uvm_map_teardown+0x1c7 sys/uvm/uvm_map.c:2496
uvmspace_free(fffffd806c1e8cb8) at uvmspace_free+0xbd sys/uvm/uvm_map.c:3420
reaper(ffff80002a837be0) at reaper+0x225 sys/kern/kern_exit.c:478
end trace frame: 0x0, count: 249
End of stack trace.
syncing disks...39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 giving up

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 0x000f27d0: 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> machine ddbcpu 0
machine: syntax error
boot> trace
| / - \ | / - \ | / booting hd0a:trace: - \ | / open hd0a:trace: No such file or directory
failed(2). will try /bsd
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

[syzbot]

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