assert "mo->ro_magic == RWLOCK_OBJ_MAGIC" failed in kern_rwlock.c

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 25b30cac31a3 sort
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=11b10bcd180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=e4019ac7b3da2a301f6a

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a2564b1f7252/disk-25b30cac.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/319d6a006bad/bsd-25b30cac.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1162abc82f00/kernel-25b30cac.xz

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

panic: kernel diagnostic assertion "mo->ro_magic == RWLOCK_OBJ_MAGIC" failed: file "/syzkaller/managers/multicore/kernel/sys/kern/kern_rwlock.c", line 599 rw_obj_free: lock 0xfffffd80642cec40: mo->ro_magic (0) != RWLOCK_OBJ_MAGIC (0x5aa3c85d)
Starting stack trace...
panic(ffffffff828aa047) at panic+0x16f sys/kern/subr_prf.c:229
rw_obj_free(fffffd80642cec40) at rw_obj_free+0x108 sys/kern/kern_rwlock.c:600
amap_free(fffffd806b59bcc8) at amap_free+0x92 sys/uvm/uvm_amap.c:454
amap_wipeout(fffffd806b59bcc8) at amap_wipeout+0x243 sys/uvm/uvm_amap.c:532
uvm_unmap_detach(ffff80002a154eb0,1) at uvm_unmap_detach+0x7d sys/uvm/uvm_map.c:1354
uvm_map_teardown(fffffd80775c3a68) at uvm_map_teardown+0x2f8 sys/uvm/uvm_map.c:2554
uvmspace_free(fffffd80775c3a68) at uvmspace_free+0xa6 sys/uvm/uvm_map.c:3461
reaper(ffff80002a148cd8) at reaper+0x197 sys/kern/kern_exit.c:463
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